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
{{ message }}
This repository has been archived by the owner on Nov 2, 2019. It is now read-only.
When a field holds an array of strings, like ApiKeys.roles, the current logic works for listing those strings (I think it just does array.toString(), which gives a comma separated list), but not for adding or editing the field. In both cases, the value is sent to the server as a single string, not an array.
I think we should have a custom field type for this, with behavior like this library. We might be able to extend chosen, which we're already using, to support this, by just adding dynamically (i.e. on keydown) an option to the choice list that's the same as the value that the user's currently typing
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When a field holds an array of strings, like
ApiKeys.roles
, the current logic works for listing those strings (I think it just doesarray.toString()
, which gives a comma separated list), but not for adding or editing the field. In both cases, the value is sent to the server as a single string, not an array.I think we should have a custom field type for this, with behavior like this library. We might be able to extend chosen, which we're already using, to support this, by just adding dynamically (i.e. on keydown) an option to the choice list that's the same as the value that the user's currently typing
The text was updated successfully, but these errors were encountered: