-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Remove gadgets functionality and update the exploration schema version accordingly. #3801
Conversation
/cc @BenHenning. The exploration migration job needs to be run for the next release. |
Codecov Report
@@ Coverage Diff @@
## develop #3801 +/- ##
===========================================
+ Coverage 45.88% 46.19% +0.31%
===========================================
Files 280 275 -5
Lines 21167 20703 -464
Branches 3293 3232 -61
===========================================
- Hits 9712 9564 -148
+ Misses 11455 11139 -316
Continue to review full report at Codecov.
|
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.
Thanks Sean!
gadget_instance = exploration.get_gadget_instance_by_name( | ||
change.gadget_name) | ||
if (change.property_name == | ||
exp_domain.GADGET_PROPERTY_VISIBILITY): |
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.
Remove this constant in exp_domain? (and GADGET_PROPERTY_CUST_ARGS)
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.
Thanks @tjiang11! I thought I put it under the "these four properties are deprecated" part, though -- is that the one you mean? The idea is to prevent others using them as keys in the future.
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.
Also, @tjiang11 -- if this sounds OK to you, please go ahead and merge. Don't want to delay it too much since this PR is large and prone to merge conflicts.
Thanks!
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.
Ohh I see, okay that makes sense
No description provided.