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
Right now when the default global constraints are changed, paths that don't have unique constraints don't update to use the new global constraints, which requires going into every path to update them. To solve this, there can be a checkbox in the global constraints options menu to use the default global constraints
The text was updated successfully, but these errors were encountered:
So the way this needs to work is a little bit weird because the settings exists higher in the tree compared to the project page, which has ownership over the paths. I did a dumb workaround, but it means that the constraints for paths using the defaults will only be updated if the project page is open when the defaults get updated, or opened after the constraints get updated.
If you have the telemetry page open then change the defaults and redeploy, nothing will actually be updated.
Right now when the default global constraints are changed, paths that don't have unique constraints don't update to use the new global constraints, which requires going into every path to update them. To solve this, there can be a checkbox in the global constraints options menu to use the default global constraints
The text was updated successfully, but these errors were encountered: