docs: Update logic placement guidelines in API architecture#17234
Open
szokeasaurusrex wants to merge 2 commits intomasterfrom
Open
docs: Update logic placement guidelines in API architecture#17234szokeasaurusrex wants to merge 2 commits intomasterfrom
szokeasaurusrex wants to merge 2 commits intomasterfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
szokeasaurusrex
requested review from
dingsdax and
stephanie-anderson
and removed request for
stephanie-anderson
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.
This section was using RFC 2119 requirement levels in a strange way. These levels are meant to designate requirement levels, but here, they were using to describe technical details of data processing features.
My change removes the strangely-used "MUST" specifiers from the examples of changes that need to live in the SDK, instead using generic "needs to" phrasing