fix: Update UI labeling: custom constraint -> (strategy) constraint #2101
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
This changes every instance of "custom constraint" to "constraint" or "strategy constraint" depending on the context.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ivarconr
approved these changes
Sep 28, 2022
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.
What
This PR changes all instances (that my grep could find) of "custom constraint" in the UI and in the documentation to either "constraint" or "strategy constraint", depending on the context. It also renames an image that was called "custom-constraint.png".
Why
It was recently discovered that there was a mismatch between the terminology in the docs and in the UI (strategy constraints and custom constraints respectively), and upon closer discussion, we found that the UI had deviated at some point.
We don't offer any other kinds of constraints, so we decided to change the wording in the UI from custom constraint to just constraint or strategy constraint depending on what would work in the context.