Open amorton opened 1 week ago
My 2 centers: I would expect options
to be a top-level property rather than as definition.options
in this case. Not a dealbreaker either way, just that's what I would expect as a developer integrating against this API.
The current create index command (for regular indexes on text, numbers etc) looks like :
NOTE: the options are under the
definition
element, the options are only there for text/ascii indexes and they areascii
,normalize
,caseSensitive
.This is per the design from sept.
But looking at this, it looks like "Unnecessary Nesting" (TM) and perhaps we should have they under the definition ?
Other than UN (see above) there is already an options clause for the command, so this is also a case of "Double Options" (TM)