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

Implement BE for US3 feature #9

Closed
AliceeLe opened this issue Sep 13, 2024 · 1 comment
Closed

Implement BE for US3 feature #9

AliceeLe opened this issue Sep 13, 2024 · 1 comment
Assignees
Labels
Milestone

Comments

@AliceeLe
Copy link

AliceeLe commented Sep 13, 2024

Estimated effort: 5-8 hours implementing, 2-3 hours debugging
Dependencies: #10
Acceptance criteria: Modularized code that is able to compile and tested upon

@AliceeLe AliceeLe changed the title Implement BE for US2 feature Implement BE for US3 feature Sep 13, 2024
This was referenced Sep 13, 2024
@AliceeLe AliceeLe self-assigned this Sep 13, 2024
@annashiheart annashiheart modified the milestones: Sprint 2, Sprint 1 Sep 13, 2024
@AliceeLe
Copy link
Author

I changed the field in the database and designed an API that mark whether the post is answered by instructor or not in public/openapi/components/schema/TopicObject.yml and public/openapi/read/index.yml.

Defining Redis fields in YAML allows for flexible configuration without modifying the application’s code. This is useful in environments where configuration might change depending on deployment contexts

Then, I implemented an API in public/openapi/write/posts/pid/answered.yaml and src/categories/answered.js. However, I am having some roadblocks. Given that we haven’t figured out how to test it, we are slow in that aspect. Furthermore, the BE isn’t connected with the FE yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants