Notes api spec#6
Open
FatemehRajabi wants to merge 9 commits intoautomationExamples:mainfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implemented a backend Notes API using a spec-driven development approach. The API supports creating notes, listing all notes, searching by keyword, and retrieving a note by ID.
Approach
SPECS/notes-api.mdprior to implementationCode Generation Tools Used
Used Claude and ChatGPT as code generation and design assistants to draft scaffolding, API route structure, and test cases. All generated code was reviewed, refined, and validated against the written spec and automated tests.
How to Run
See README for installation, run, and test instructions.