-
Notifications
You must be signed in to change notification settings - Fork 3.8k
83862 tags settings v2 #90453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
huult
wants to merge
9
commits into
Expensify:main
Choose a base branch
from
huult:83862-tags-settings-v2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
83862 tags settings v2 #90453
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
56bebca
migrate SETTINGS_TAGS_EDIT
huult 4edbb23
migrate tags settings
huult 182446c
remove type unused
huult 70dc030
Merge remote-tracking branch 'upstream/main' into 83862-tags-settings-v2
huult a5e76f8
Merge remote-tracking branch 'upstream/main' into 83862-tags-settings-v2
huult e203c87
update eslint
huult 94c6332
Merge remote-tracking branch 'upstream/main' into 83862-tags-settings-v2
huult 0f51d48
Merge remote-tracking branch 'upstream/main' into 83862-tags-settings-v2
huult 297ac3c
updat testID
huult File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we need the OldRoute mapping?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mananjadhav I’m not sure when we should update the route to the old route. In all migration cases where we change the route path, do we always update it to the old route, or are there cases where we actually need to set an oldRoute?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think @mjasikowski would be better to answer. My thoughts are if the links are sent over chat then having the migration mapping really helps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, mappings should be made for all migrated routes that differ from the static ones. While in some cases it might be impossible, it's better to do it in this specific case, as there shouldn't be any mapping issues here 😄
I checked, and this mapping works correctly:
/settings/*/tag/*/*': '/settings/$1/tags/tag-settings/$2/$3.Also, please check if the migrated routes differ from the static ones elsewhere in this PR, and if so, try to add mappings for them too 🙌