[FIX] sheet: Avoid divergent sheet names in collaborative #5090
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.
Similar issue to the one raised in #5010. If 2 userrs with different languages (i.e. different translation schemes), importing a sheet data without a name could result in different outcomes for both users.
Currently, this is not an issue because the sheet data are 'fixed' upstream by the migration mecanism but this might change/disappear in the future.
Task: 0
Description:
description of this task, what is implemented and why it is implemented that way.
Task: TASK_ID
review checklist