Skip to content
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

Fixed bug in LocationDrawer sceneId logic #9480

Merged
merged 1 commit into from Dec 21, 2023
Merged

Conversation

barankyle
Copy link
Member

Summary

Location sceneId's are now projects//.scene.json Select for sceneId is just / Setting of state.scene in LocationDrawer.tsx was erroring since there were no matches, and then would prepend projects/ and append .scene.json to the sceneId if saved without touching the scene selector, which would then point the location to an invalid scene.

References

closes #insert number here

QA Steps

Location sceneId's are now projects/<projectName>/<sceneName>.scene.json
Select for sceneId is just <projectName>/<sceneName>
Setting of state.scene in LocationDrawer.tsx was erroring since there were no
matches, and then would prepend projects/ and append .scene.json to the sceneId
if saved without touching the scene selector, which would then point the location
to an invalid scene.
@HexaField HexaField merged commit 0e88c2d into dev Dec 21, 2023
13 checks passed
@HexaField HexaField deleted the location-drawer-sceneid-fix branch December 21, 2023 23:58
Rezmason pushed a commit that referenced this pull request Dec 26, 2023
Location sceneId's are now projects/<projectName>/<sceneName>.scene.json
Select for sceneId is just <projectName>/<sceneName>
Setting of state.scene in LocationDrawer.tsx was erroring since there were no
matches, and then would prepend projects/ and append .scene.json to the sceneId
if saved without touching the scene selector, which would then point the location
to an invalid scene.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants