-
Notifications
You must be signed in to change notification settings - Fork 545
Blueprint save/load test #11395
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
Blueprint save/load test #11395
Conversation
Web viewer built successfully.
Note: This comment is updated whenever you push a commit. |
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.
nice!! very happy to see this automated now
// Trigger recalculation of visualizable entities and blueprint overrides. | ||
test_context.setup_viewport_blueprint(|_ctx, _blueprint| {}); |
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.
oof that's the annoying thing you've mentioned on yesterday standup where App is recalculating it all the time and TestContext
is not? Feels like TestContext
is in the wrong here, but I figure we can't do that where test context's run method lives or something of that shape?
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.
Yes, it is. :(
The new App
-based harness work differently, it loads the current blueprint from the store at the start of each frame. The TestContext
only does that when you explicitly call this function.
Related
What
Adds save/load/snapshot tests for blueprints.
Note: the
check_rbl_import.py
can't yet be removed as it's testing blueprint imports with a different app id, this test doesn't cover it yet, this is whereApp
andTestContext
differ somewhat.