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
This is a pretty aggressive contract which ensures that you're not trying to load a vector map designed to work with some other version of Ground Control. It's arguably a desirable behavior while we're learning the downstream effects of updating GC's vector vocabulary.
Is it too strict? Should we loosen it up and allow vector maps which describe a valid subset of our vector vocabulary?
The text was updated successfully, but these errors were encountered:
This is a pretty aggressive contract which ensures that you're not trying to load a vector map designed to work with some other version of Ground Control. It's arguably a desirable behavior while we're learning the downstream effects of updating GC's vector vocabulary.
Is it too strict? Should we loosen it up and allow vector maps which describe a valid subset of our vector vocabulary?
The text was updated successfully, but these errors were encountered: