Outreachy 2022 Ideas
This page is part of Outreachy2022 it exposes ideas to decide what we should do.
- Extending the existing documentation in POD format.
- refactor parts with inlined CSS and JS
- make project accessible to more developers
- improve onboarding documentation
- IDE integration and debugging
- live reload
- Add integrations tests covering the API:
- API is a good entry for integrations tests, it's generally clear what to expect
- As project GSOD2022 API documentation will document, it would be cool to insure we never break the API
- Add tests to prevent URLs from breaking.
- Refactor the routing code:
- current routing code is a bit messy (see display.pl) as it does not separate concerns well, and it's very difficult to understand in which function an url will land
- maybe it could be a good idea to progressively re-implement this part using mojolicious (url by url)
- refactoring also means adding more documentation
- Move taxonomies to their own submodules
- Refactoring our current taxonomy unit tests. Updated taxonomies can make unit tests break easily. We shouldnât need to change the unit tests each time we update taxonomies. The new tests would work on âconceptsâ.
- Refactoring ingredient parsing and adding support for nested ingredients and more patterns (so that they can be applied to more languages)
- Implementing a UI âtest â generatorâ that enables non-programmers to add a test that fails until correction in ingredient analysis is implemented when they stumble upon problems.
- Show a prompt when the ingredient list photo has changed, but not the ingredient list itself.
- Implement more checks and form validation when users enter data (for example nutritional data)
- Limit the number of times new products without barcodes can be added by a certain IP Address.
- Implementing autocorrect and spelling checks in the product edit form.
- Support for Hindi language