Linting and API foundation for Bloom
By RepoJournal , from @bgrgndzz's public GitHub activity
Backfilled
Buğra Gündüz set up ESLint across the project and wired together the client and backend with axios, while adding schema constraints and pagination to the API.
Work on bgrgndzz/bloom spanned tooling, routing, and backend structure. Gündüz set up ESLint [1] to enforce code style across the codebase. On the frontend side, he changed the initial route to Topics [2] and refactored the client to use axios [3] instead of its previous HTTP approach, simplifying request handling throughout the application. On the backend, he added the unique property to mongoose schemas where necessary [4], enforcing data constraints at the database level. He added temporary web pages [5] to support ongoing development and added default pagination to the profile API endpoints [6], ensuring consistent behavior when clients request user profile data.
One email a day. Unsubscribe in one click.
A short briefing every day bgrgndzz ships something — in about 3 minutes.
One email a day. Unsubscribe in one click. Read a past issue →
References
- [1] setup eslint bgrgndzz/bloom
- [2] change the initial route to Topics bgrgndzz/bloom
- [3] refactor for axios bgrgndzz/bloom
- [4] add the unique property to mongoose where necessary bgrgndzz/bloom
- [5] add temporary web pages bgrgndzz/bloom
- [6] add default page to profile api endpoints bgrgndzz/bloom