You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary
When a file is duplicated, bridge. saves the new file's identifier or file name twice, overwriting the identifier or file name for the file that was duplicated. This can be seen for auto-completions such as in LANG files, where the file that was the result of duplicating will show up twice. This can be fixed via resetting bridge.'s cache in the behavior pack sidebar.
To Reproduce
Steps to reproduce the behavior:
Create a file (block, entity, etc.)
Give it an identifier, save the file, and close it
Duplicate the file and give the new file a different identifier
Check auto-completions where identifiers or file names are used (such as LANG file)
Observe duplicate identifier, and absence of identifier for the file that was duplicated
Observed behavior
The new file from the duplication has its identifier or file name saved twice, while the original file in the duplication no longer has its identifier or file name saved.
Expected behavior
The identifier/file name for the new file should be saved once, and the original file's identifier/file name should stay saved.
Platform
OS: Windows 10
App Version: 1.7.18
Additional context
As mentioned above, the cache issue can be solved by refreshing bridge.'s cache, but this will not prevent the bug in the future (unless the cache is refreshed again).
The text was updated successfully, but these errors were encountered:
Summary
When a file is duplicated, bridge. saves the new file's identifier or file name twice, overwriting the identifier or file name for the file that was duplicated. This can be seen for auto-completions such as in LANG files, where the file that was the result of duplicating will show up twice. This can be fixed via resetting bridge.'s cache in the behavior pack sidebar.
To Reproduce
Steps to reproduce the behavior:
Observed behavior
The new file from the duplication has its identifier or file name saved twice, while the original file in the duplication no longer has its identifier or file name saved.
Expected behavior
The identifier/file name for the new file should be saved once, and the original file's identifier/file name should stay saved.
Platform
Additional context
As mentioned above, the cache issue can be solved by refreshing bridge.'s cache, but this will not prevent the bug in the future (unless the cache is refreshed again).
The text was updated successfully, but these errors were encountered: