Updated the TODO to include CAEP usecases #92
Closed
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
Updated the TODO to include CAEP usecases
tulshi
reviewed
Aug 29, 2023
|
|
||
| The CAEP use cases that set the requirements are described in CAEP Use Cases (TODO: Add | ||
| reference when file is added to repository.) | ||
| The CAEP use cases that set the requirements are described in CAEP Use Cases {{CAEP}}. |
Contributor
There was a problem hiding this comment.
This was supposed to be a separate use-cases doc. There was a working doc, but it never made it to the repo (needed more work I guess)
Contributor
Author
|
Abandoning it |
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.
Updated the TODO to include CAEP usecases