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.

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

refactoring project use cases #79

Merged
merged 5 commits into from
Aug 12, 2023
Merged

refactoring project use cases #79

merged 5 commits into from
Aug 12, 2023

Conversation

SoumyadipSarker
Copy link
Contributor

Some changes were made to the project use cases and refactoring was done. Test cases were also written, although deleteProject and deleteprojectTest has several imporant problems.

Copy link
Contributor

@rtutz rtutz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes are helpful in ensuring actual entities are changed as opposed to entity models for the Project Selection.

Here are some thoughts:
I think Wendy had the idea of storing all the project entities from the database in a new class (like currentProjectRepository). I think this might be the best option.
With this approach, we might have an ArrayList of all the project entities. If one needs to get deleted, we just delete that project entity from the list.

Is there a way in the testing such that we can create a fake projects.csv with only one entry with some id, then delete it and check whether it is valid or not?

@rtutz rtutz merged commit 78cadb3 into main Aug 12, 2023
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants