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
Currently, there is a constraint in the base GraphObject schema that all graph object _key values must be at minimum 10 characters. This has lead to some integration developers adding artificial prefixes at the beginning of _key values just to avoid it.
We should consider reducing the constraint to a single character or at least reducing the constraint lower than 10 characters.
I agree, that constraint should be removed. We should be able to count on the the combination of _type and _key (scope, really) to prevent duplicates, as the key tracker does for us.
Currently, there is a constraint in the base
GraphObject
schema that all graph object_key
values must be at minimum 10 characters. This has lead to some integration developers adding artificial prefixes at the beginning of_key
values just to avoid it.We should consider reducing the constraint to a single character or at least reducing the constraint lower than 10 characters.
cc @aiwilliams @ndowmon @mknoedel
The text was updated successfully, but these errors were encountered: