-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Enhancement: Taxonomy output type setting #273
Comments
Just want add a +1 here. I tried making a taxonomy because I would love to look at posts by their "post_type" but I cant do this without converting post_type to an array with a limit of one and thats not an easy lift with some automation I am using. |
This functionality will be added by the new By default, it will be set to |
@cvburgess you are able to give it a try in the latest beta version. Example field configuration: {
"title": "tags",
"name": "tags",
"type": "tags",
"taxonomyLimit": 1,
"singleValueAsString": true
},
{
"title": "categories",
"name": "categories",
"type": "categories",
"taxonomyLimit": 1,
"singleValueAsString": true
},
{
"title": "Custom taxonomy",
"name": "customTags",
"type": "taxonomy",
"taxonomyId": "customTaxonomy",
"taxonomyLimit": 1,
"singleValueAsString": true
} |
That worked PERFECTLY for me - thank you SO MUCH! |
Happy to hear! |
This is a great enhancement, as a CMS requires user inputs to match rules in the code. As a further enhancement, it may be beneficial to allow setting the type to a string or an array. Because this is a developer concern, it may be good enough to assume that a limit of a single selection would be a string. A markdown front-matter structure has limited data types available, and I believe that enforcing a data type would make this more robust. Target parsers will output data differently based on these types. Thanks!
Originally posted by @johnfuller in #241 (comment)
The text was updated successfully, but these errors were encountered: