Enum data source filtering

[McGern]

Hi,

Am using the Enum datasource with the DataListItem attributes, and was wondering if the "Group" property (or something else?) could be used somehow to define a filter for the enums? Similar to how jsonpath can be used to filter json data sources.

Use case is something like this:-

• Large list of enums to define something like "Text font style" which can range from a selection of "Heading", "Subheading" and "Body", where you might have multiple of each type e.g. "Heading 1"
• This enum can be used in a Text tag helper
• The content editor has properties for heading, subheading and body copy on a document type
• The content editor has options for styling the properties, but can only select an appropriate size.

Kind regards,
Jarrod

[leekelleher]

@McGern Thank you for the suggestion.

So I can visual it better, would you be able to provide an example of such an Enum (C#)?

From how I understand it so far, it sounds like there could be unrelated data inside a single Enum structure. 🤔

[McGern]

Hi @leekelleher,

Example might be something like this

public enum FontStyleEnum
{
DisplayTextHero,
DisplayText1,
DisplayText2,
DisplayText3,
DisplayText4,
DisplayText5,
HeadingText1,
HeadingText2,
HeadingText3,
SubheadingText1,
SubheadingText2,
BodyTextLarge,
BodyTextNormal,
BodyTextSmall,
None
}

This could be consumed in tag helpers where the property is the strongly typed enum where the developer gets intellisense to choose from any of the values. In this case, the enum value is translated into a css class.

When using this enum as a picker in Umbraco we could have 3 different fields for
Heading Text
Subheading Text
Body Text

And a style selector for each, where ideally the user can only choose from a limited selection from the enum
e.g. Heading text can only select a style from one of the "Display" or "Heading"

Because enums can't be (shouldn't be) combined from subsets, it needs to be a single large list which represents all font styles used (regardless of grouping).

Using Enums are a better developer experience than relying on arbitrary string values, mostly in the cases where the enum isn't always consumed from umbraco content.

I am currently using the json datasource, where the json is generated from the css classes with the class being the value, and the jsonpath is used to create 3 different datatypes. This is a bit clunky and not entirely intuitive - so have been looking at the enum datasource.