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 prerequisite for moving more stuff from schema onto collection, as users will need a means to set the moved properties.
Should eventually allow the setting of indexes and ACP stuff too, but it is fine to block those off initially in order to reduce scope of the initial PR.
As the only to-be mutable property that is not index/acp and currently already on collection description is col/field name, and those properties comes with higher risk, it might be best to do this alongside #1386 or #1385 to keep things simple to start off with.
The text was updated successfully, but these errors were encountered:
## Relevant issue(s)
Resolves#2389
## Description
Adds the PatchCollection command.
Mutating anything but the collection name is currently disabled, we can
expand this as we see fit, but for now I'd prefer to keep the initial PR
small.
This change means that the Collection Name is no longer always going to
be the same as the Schema Name.
Like
PatchSchema
, but forCollectionDescription
s.This is a prerequisite for moving more stuff from schema onto collection, as users will need a means to set the moved properties.
Should eventually allow the setting of indexes and ACP stuff too, but it is fine to block those off initially in order to reduce scope of the initial PR.
As the only to-be mutable property that is not index/acp and currently already on collection description is col/field name, and those properties comes with higher risk, it might be best to do this alongside #1386 or #1385 to keep things simple to start off with.
The text was updated successfully, but these errors were encountered: