MomentMeal is a marketplace for food and recipes. We help you find and create the best recipes and meal plans for you.
Home Page: https://momentmeal.com/
License: GNU Affero General Public License v3.0
Built with the Next.js App Router, tRPC, TypeScript, Prisma & Tailwind
This project has taken inspiration from the following projects:
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
![imgbot[bot] avatar](https://avatars.githubusercontent.com/in/4706?v=4 "imgbot[bot]")
As a developer I would like to be able to create a new collection, so I can quicker get to developing the actual collectionand not write all the boilerplate code.
No response
MINOR
As a developer, I would like to worry less about the paths to my imports, so I can more easily create new imports and understand the current imports.
Use path mapping to simplify imports instead of using relative paths
No UX needed.
DOR
- Acceptance criteria written and reviewed by QA, PM and SE
- Behaviour scenarios written
- Signed off UX
- Estimated and appropriately scoped
DOD
- Test complete
- Merged to master
- Unit tests on all new code (80% coverage)
- Integration tests for endpoints / web sockets
- End-to-end or integration tests verifying acceptance criteria
- Code complete
- Peer reviewed (1 person/people)
- Follows BHelpful code standards / versioning guidelines
- No commented out code or TODOs
- TSLint / Sonarqube exceptions have explicit explanations
- Verified by QA
- Functionally manually verified on a setup like the actual setup
- QA verifies test coverage aligns with master test plan
- Verified by UX and product owner / verified by the team
- Documentation of tech debt
- Persistent technical documentation updated / written
- Ready is updated / written
The website is currently missing the recipe showcase underneath the meal plan
Add the structure for the recipe showcase.
The task is to cleanup, implement the missing features from the muck-up and make it all interactive.
As a little add-on for the create meal plan box, it is missing the line divider
This task is for the 2 recipe showcases (Browse recipes and My collection)
Implement loading screen for when API calls or similar takes long(er) time to execute
CSS background or something maybe an overlay or blurred out background
No response
Create basic Epic issue Form that allows to easily create new epics with the same structure and the Epic label.
No response
DOR
- Acceptance criteria written and reviewed by QA, PM and SE
- Behaviour scenarios written
- Estimated and appropriately scoped
DOD
- Test complete
- Merged to master
- Unit tests on all new code (80% coverage)
- Integration tests for endpoints / web sockets
- Code complete
- Peer reviewed (1 person/people)
- Follows BHelpful code standards / versioning guidelines
- No commented out code or TODOs
- TSLint / SonarCloud exceptions have explicit explanations
- Verified by QA
- Functionally manually verified on a setup like the actual setup
- QA verifies test coverage aligns with master test plan
- Documentation of tech debt
- Persistent technical documentation updated / written
- Ready is updated / written
Expected look:
Current look:
Add generators to create files and file structures that we use all the time to speed up the development process.
As a developer, I would not like to get all values, that should be hidden from the API like a user's password.
No response
DOR
- Acceptance criteria written and reviewed by QA, PM and SE
- Behaviour scenarios written
- Estimated and appropriately scoped
DOD
- Test complete
- Merged to master
- Unit tests on all new code (80% coverage)
- Integration tests for endpoints / web sockets
- Code complete
- Peer reviewed (1 person/people)
- Follows BHelpful code standards / versioning guidelines
- No commented out code or TODOs
- TSLint / SonarCloud exceptions have explicit explanations
- Verified by QA
- Functionally manually verified on a setup like the actual setup
- QA verifies test coverage aligns with master test plan
- Documentation of tech debt
- Persistent technical documentation updated / written
- Ready is updated / written
MAJOR
As a user I would like to be able to add a side dish to my recipe, so that my recipes can be easier to follow with grouped recipes (side dishes and main dish)
No response
As a developer I would like to have the Node project placed in the root of the repo to reduce the amount of steps needed to start development each time.
No response
DOR
- Acceptance criteria written and reviewed by QA, PM and SE
- Behaviour scenarios written
- Estimated and appropriately scoped
DOD
- Test complete
- Merged to master
- Unit tests on all new code (80% coverage)
- Integration tests for endpoints / web sockets
- Code complete
- Peer reviewed (1 person/people)
- Follows BHelpful code standards / versioning guidelines
- No commented out code or TODOs
- TSLint / SonarCloud exceptions have explicit explanations
- Verified by QA
- Functionally manually verified on a setup like the actual setup
- QA verifies test coverage aligns with master test plan
- Documentation of tech debt
- Persistent technical documentation updated / written
- Ready is updated / written
This task is to complete the create recipe UI.
The window for adding a recipe to the meal plan manually is missing.
Add it, so it shows, when the user clicks the add recipe option or when the user changes an existing recipe in the plan to another.
MAJOR
As a user I would like to be able to change my user settings so that I can tailor my experience of using the product to my liking.
This is the current look
MINOR
As a developer, I would like to have a place to go to, where I can read about all things development of the project, so I can more easily get to developing the actual features.
No UX needed.
No response
DOR
- Acceptance criteria written and reviewed by QA, PM and SE
- Behaviour scenarios written
- Signed off UX
- Estimated and appropriately scoped
DOD
- Test complete
- Merged to master
- Unit tests on all new code (80% coverage)
- Integration tests for endpoints / web sockets
- End-to-end or integration tests verifying acceptance criteria
- Code complete
- Peer reviewed (1 person/people)
- Follows BHelpful code standards / versioning guidelines
- No commented out code or TODOs
- TSLint / Sonarqube exceptions have explicit explanations
- Verified by QA
- Functionally manually verified on a setup like the actual setup
- QA verifies test coverage aligns with master test plan
- Verified by UX and product owner / verified by the team
- Documentation of tech debt
- Persistent technical documentation updated / written
- Ready is updated / written
MAJOR
As a developer I would like to be able to create a new react component, so I can quicker get to developing the actual component and not write all the boilerplate code.
No UX needed.
No response
The 2 functionalities that is missing, is adding to collection and clicking to open the recipe itself.
When a user clicks the plus icon, it should change to a checkmark icon to show the user, it has been added to the user's collection.
When a user clicks the recipe box itself, it should take the user to the show recipe page.
As a developer I would like to be able to create a new utility, so I can quicker get to developing the actual utility and not write all the boilerplate code.
No response
The web app is missing this feature for the create meal plan
Add it
As a developer, I would like to be able to get all or a subset of a user's recipes, so that I can display them in a UI.
Find multiple documents
Limit the Number of Returned Results
As a developer, I would like to have a place to go to, where I can read about all things development of the project, so I can more easily get to developing the actual features.
No response
DOR
- Acceptance criteria written and reviewed by QA, PM and SE
- Behaviour scenarios written
- Estimated and appropriately scoped
DOD
- Test complete
- Merged to master
- Unit tests on all new code (80% coverage)
- Integration tests for endpoints / web sockets
- Code complete
- Peer reviewed (1 person/people)
- Follows BHelpful code standards / versioning guidelines
- No commented out code or TODOs
- TSLint / SonarCloud exceptions have explicit explanations
- Verified by QA
- Functionally manually verified on a setup like the actual setup
- QA verifies test coverage aligns with master test plan
- Documentation of tech debt
- Persistent technical documentation updated / written
- Ready is updated / written
As a developer I would like to be able to create a new middleware, so I can quicker get to developing the actual middleware and not write all the boilerplate code.
No response
MAJOR
As a developer, I would like to have the complete codebase for MealPlanr in one repo to simplify additions, builds, tests etc.
No UX
No response
DOR
- Acceptance criteria written and reviewed by QA, PM and SE
- Behaviour scenarios written
- Signed off UX
- Estimated and appropriately scoped
DOD
- Test complete
- Merged to master
- Unit tests on all new code (80% coverage)
- Integration tests for endpoints / web sockets
- End-to-end or integration tests verifying acceptance criteria
- Code complete
- Peer reviewed (1 person/people)
- Follows BHelpful code standards / versioning guidelines
- No commented out code or TODOs
- TSLint / Sonarqube exceptions have explicit explanations
- Verified by QA
- Functionally manually verified on a setup like the actual setup
- QA verifies test coverage aligns with master test plan
- Verified by UX and product owner / verified by the team
- Documentation of tech debt
- Persistent technical documentation updated / written
- Ready is updated / written
The recipe box for the private page needs to look like the following
The recipe box for the public page needs to look like the following
Current look
Special for the private recipe box
Special for the public recipe box
MAJOR
As a developer I would like to be able to create a new Cypress test, so I can quicker get to developing the actual Cypress test and not write all the boilerplate code.
No UX needed.
No response
As a developer, I would like to be able to get all or a subset of public recipes, so that I can display them in a UI.
No response
CodeFactor found an issue: Complex Code
It's currently on:
app\src\components\selectionArea\SelectionArea.tsx
Expected look
Current look
As a developer I would like to get a response of the complete object I requested and not a semi-complete with IDs as references to other objects.
Session route does not need to be populated, since the purpose of the session isn't to get the user's information, but to get information on wether the user has a valid login or not; whereas, recipe needs to get all the information on the recipe, meaning it needs to get all the ingredients but also the user information, as the user should be displayed in relation to the recipe on the website.
DOR
- Acceptance criteria written and reviewed by QA, PM and SE
- Behaviour scenarios written
- Estimated and appropriately scoped
DOD
- Test complete
- Merged to master
- Unit tests on all new code (80% coverage)
- Integration tests for endpoints / web sockets
- Code complete
- Peer reviewed (1 person/people)
- Follows BHelpful code standards / versioning guidelines
- No commented out code or TODOs
- TSLint / SonarCloud exceptions have explicit explanations
- Verified by QA
- Functionally manually verified on a setup like the actual setup
- QA verifies test coverage aligns with master test plan
- Documentation of tech debt
- Persistent technical documentation updated / written
- Ready is updated / written
This issue is the changes needed for the settings page.
Possible new logo and animation.
No response
No response
As a developer I would like to log the test coverage to a service lige CodeCov in order to have an overview of the coverage and also to reach the goal of 80% code coverage for SonarCloud.
No response
- Acceptance criteria written and reviewed by QA, PM and SE
- Behaviour scenarios written
- Estimated and appropriately scoped
- Test complete
- Merged to master
- Unit tests on all new code (80% coverage)
- Integration tests for endpoints / web sockets
- End-to-end or integration tests verifying acceptance criteria
- Code complete
- Peer reviewed (2 people)
- Follows Helpful code standards / versioning guidelines
- No commented out code or TODOs
- TSLint / Sonarqube exceptions have explicit explanations
- Verified by QA
- Functionally manually verified on a setup like the actual setup
- QA verifies test coverage aligns with master test plan
- Verified by product owner / verified by the team
- Documentation of tech debt
- Persistent technical documentation updated / written
- Ready is updated / written
Add generators to create files and file structures that we use all the time to speed up the development process.
Implement example text for all models in swagger
Current behaviour:
Expected behaviour:
No response
MINOR
As a developer I would like to have the Node project placed in the root of the repo to reduce the amount of steps needed to start development each time.
No UX needed.
No response
DOR
- Acceptance criteria written and reviewed by QA, PM and SE
- Behaviour scenarios written
- Signed off UX
- Estimated and appropriately scoped
DOD
- Test complete
- Merged to master
- Unit tests on all new code (80% coverage)
- Integration tests for endpoints / web sockets
- End-to-end or integration tests verifying acceptance criteria
- Code complete
- Peer reviewed (1 person/people)
- Follows BHelpful code standards / versioning guidelines
- No commented out code or TODOs
- TSLint / Sonarqube exceptions have explicit explanations
- Verified by QA
- Functionally manually verified on a setup like the actual setup
- QA verifies test coverage aligns with master test plan
- Verified by UX and product owner / verified by the team
- Documentation of tech debt
- Persistent technical documentation updated / written
- Ready is updated / written
If any recipe can be made public, that means that there could be introduced many duplicate recipes in the public browse recipes section.
This is mostly a big problem as the user can take a public recipe, and add it to their own collection. If there were no restrictions, the user could then just make their copied version public resulting in 2 identical recipes in the public browsing area.
Add requirements to make a recipe public
?
MAJOR
As a developer I would like to be able to create a new redux reducer, so I can quicker get to developing the actual reducer and not write all the boilerplate code.
No UX needed.
No response
MAJOR
As a developer, I would like to have a generator setup, in which I am able to create generators for different parts of the project.
No UX needed.
No response
DOR
- Acceptance criteria written and reviewed by QA, PM and SE
- Behaviour scenarios written
- Signed off UX
- Estimated and appropriately scoped
DOD
- Test complete
- Merged to master
- Unit tests on all new code (80% coverage)
- Integration tests for endpoints / web sockets
- End-to-end or integration tests verifying acceptance criteria
- Code complete
- Peer reviewed (1 person/people)
- Follows BHelpful code standards / versioning guidelines
- No commented out code or TODOs
- TSLint / Sonarqube exceptions have explicit explanations
- Verified by QA
- Functionally manually verified on a setup like the actual setup
- QA verifies test coverage aligns with master test plan
- Verified by UX and product owner / verified by the team
- Documentation of tech debt
- Persistent technical documentation updated / written
- Ready is updated / written
As a developer, I would like to have a generator setup, in which I am able to create generators for different parts of the project.
No response
DOR
- Acceptance criteria written and reviewed by QA, PM and SE
- Behaviour scenarios written
- Estimated and appropriately scoped
DOD
- Test complete
- Merged to master
- Unit tests on all new code (80% coverage)
- Integration tests for endpoints / web sockets
- Code complete
- Peer reviewed (1 person/people)
- Follows BHelpful code standards / versioning guidelines
- No commented out code or TODOs
- TSLint / SonarCloud exceptions have explicit explanations
- Verified by QA
- Functionally manually verified on a setup like the actual setup
- QA verifies test coverage aligns with master test plan
- Documentation of tech debt
- Persistent technical documentation updated / written
- Ready is updated / written
As a developer, I would like to worry less about the paths to my imports, so I can more easily create new imports and understand the current imports.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.
