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
The Name field is (and should remain) unique, but we don't necessarily want to require the user to set it.
The Display Name is what the user should enter as input, and it is not required to be unique in our system.
Part 1:
The schema should be updated to be Optional() and NotEmpty() for both fields, e.g.:
Updated Organization Schema:
Comment("the name of the organization").
MaxLen(orgNameMaxLen).
++ Optional().
NotEmpty().
Annotations(
entgql.OrderField("name"),
entgql.Skip(entgql.SkipWhereInput),
),
field.String("display_name").
Comment("The organization's displayed 'friendly' name").
MaxLen(nameMaxLen).
++ Optional().
++ NotEmpty().
Annotations(
entgql.OrderField("display_name"),
),
Part 2
If the Name isn't provided, we should come up with a good format so that it remains human readable + unique.
The text was updated successfully, but these errors were encountered:
Summary
The
Name
field is (and should remain) unique, but we don't necessarily want to require the user to set it.The
Display Name
is what the user should enter as input, and it is not required to be unique in our system.Part 1:
The schema should be updated to be
Optional()
andNotEmpty()
for both fields, e.g.:Updated Organization Schema:
Part 2
If the
Name
isn't provided, we should come up with a good format so that it remains human readable + unique.The text was updated successfully, but these errors were encountered: