Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change CTM enum filters to use list from model settings instead of string #5570

Closed
1 of 2 tasks
derrickmehaffy opened this issue Mar 23, 2020 · 0 comments
Closed
1 of 2 tasks
Labels
issue: enhancement Issue suggesting an enhancement to an existing feature severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve source: core:content-manager Source is core/content-manager package

Comments

@derrickmehaffy
Copy link
Member

  • I have created my request on the Product Board before I submitted this issue
  • I have looked at all the other requests on the Product Board before I submitted this issue

Please describe your feature request:

Currently the filters for enumeration values is using a string, since enumerations can't be changed in production (or without the server restarting) the CTM should be using the values configured in the model settings file and giving a drop down list.

I'd imagine this would also provide a bit of ground work when the relational values in the list view feature is added as well.

@lauriejim lauriejim added severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve source: core:content-manager Source is core/content-manager package issue: enhancement Issue suggesting an enhancement to an existing feature labels Mar 24, 2020
soupette added a commit that referenced this issue Mar 27, 2020
Signed-off-by: soupette <cyril.lpz@gmail.com>
@strapi strapi locked as resolved and limited conversation to collaborators Apr 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue: enhancement Issue suggesting an enhancement to an existing feature severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve source: core:content-manager Source is core/content-manager package
Projects
None yet
Development

No branches or pull requests

2 participants