Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Split up vulnerabilities Django app #122

Closed
haikoschol opened this issue Oct 22, 2019 · 1 comment
Closed

Split up vulnerabilities Django app #122

haikoschol opened this issue Oct 22, 2019 · 1 comment
Assignees
@haikoschol
Labels
enhancement
Milestone
Core data collection

Comments

@haikoschol
Copy link
Collaborator

Having a few small "apps" instead of a single one could make it easier for new contributors to navigate the codebase. It would also reduce coupling between different parts of the code that can be kept separate. For example, at the moment the tests for the API call code from the data import. This makes it difficult for someone not familiar with the entire codebase to diagnose test failures.

I propose to have at least two different apps to start with: One for the data import and one for the API. Later we might add apps with an actual frontend part, for example for data curation.
@pombredanne pombredanne added this to the Core data collection milestone Dec 3, 2019
@haikoschol haikoschol self-assigned this Dec 6, 2019
@haikoschol haikoschol mentioned this issue Dec 11, 2019
Closed
@haikoschol
Copy link
Collaborator Author

Partially covered by #147, the rest is of questionable utility at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@haikoschol haikoschol

Labels
enhancement
Projects
None yet
Milestone
Core data collection
Development

Successfully merging a pull request may close this issue.

Split monolithic "vulnerabilities" Django app haikoschol/vulnerablecode
2 participants
@haikoschol @pombredanne