Food static data plugin — list of big steps
Published in
2 min readFeb 17, 2019
Learn more about our groceristar-fetch
` plugin here: https://medium.com/groceristar/groceristar-fetch-small-module-that-weve-created-8b4a62bd5d7b
Learn more about how our Machine Learning team building image recognition script in order to increase the number of shopping lists:
Plugin goals
- Migration to ES6. Details: https://medium.com/groceristar/static-food-data-plugin-transition-to-es6-559d0d941ec6
- Code reorganization. Details: https://medium.com/groceristar/static-food-data-third-part-structu-615c39dcf328
- Separate basic food static files(Recipes, Grocery Lists, Ingredients, Food Attributes) with autogenerated files
- Setup collaboration between JS team and ML team members
- Move away documentation website in order to have the ability to update it more frequently
- Review some libraries, that can improve our code quality
- Try to setup translation of our data into other languages
- Reduce the number of tasks that we working on, by applying more resources
- Import recipes to our Loopback server
- Import a new set of data, that was prepared 6 months ago
- Create better test coverage for our methods. It will improve code quality
- Merge data that we have from different sources and remove duplicates in a smart way
Progress Report
- Documentation was moved away into the separated repository. Not finished. Working on auto-deploy after code changes
- Static data will have a separated website with a good explanation. Right now I set up a blank website, using GatsbyJS
- We moved away from
groceristar-fetch
` plugin first part of static data and connect it as a separated npm module. This major change was tested and published an npm too