Repository navigation
profile: describe the record check as checking our own work - #55
Merged
Merged
Conversation
The read-back catches our mistakes, not a dishonest app. Reword the quickstart paragraph and the fault-test row, and move the row's claim binding to the new wording.
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
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.
The record check is there to catch our own mistakes: a wrong field, a wrong record, a missed keystroke, a step that ran too early. Three lines of the org profile framed it around the app's success message instead.
benchmark-claims.jsonentries bound to that row now use the new context string.