naming: Use 'cff' everywhere, not CFF #29
Merged
Conversation
This file contains 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
sywhang
approved these changes
Oct 24, 2022
abhinav
added a commit
that referenced
this pull request
Oct 24, 2022
This takes a pass over the API reference for cff, updating some outdated sections and rewording others for better flow and understanding. Some docs specifically only referenced flows, but now they need to account for flows and parallels. Further, for things like scheduler.go which only re-exports APIs for ease in code generation, document that those components may change their APIs unexpectedly even if we don't intend to do that. Depends on #29 Refs #1
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.
"CFF" doesn't stand for anything, so use "cff" as a word everywhere.
Refs #1