codex-status-go prototype docs #19
Draft
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
marcinczenko
changed the title
1 task
marcinczenko
force-pushed
the
spec/codex-status-go-prototype
branch
from
281760c to
886144a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As a starting point for the spec we could use our proposal. It already provides background and draft of the solution.
TBD: add more explicit assumptions and the corresponding requirements
I would suggest to wait with adding too much details till we have a prototype that still uses Codex REST API. At that point we can also start adding specs for the Codex Lib (codex-storage/nim-codex#1220).