I have an exclusion list configuration option, for people to specify classnames they want to exclude from the list, but can't be bothered to make the regex more complicated to unmatch it; so most of the time this field wil be blank, setting it to view 'textstring' it throws an error 'value cannot be empty' if it is left blank:
Just wondering if I was missing something obvious:to make the setting 'nullable'
{
label: "Exclusion list",
description: "comma delimited list of styles to exclude",
key: "excludeList",
view: "textstring"
}
If you can, I'd suggest trying this with a nightly build and seeing if you still get the same issue. I saw some bugs in 7.0 with leaving certain properties blank, this may be a similar bug, and from what I saw at least some have been fixed in the latest builds.
that is odd, the view itself, doesn't contain any validation at all, you dont have any dublicate entries in that manifest?
- Care to share it so I can reproduce?
Alright, so it wasnt you who were doing something stupid, it was our pre-value validation.
So basically, if you add validation to any of the fields, this validation was triggered against all fields. I've already committed a fix for it, so tomorrow morning there will be a nightly build with this fix in, and its also included in 7.0.1 ofcourse.
If you want the fix now, you need to build from source (from the 7.0.1 branch) - or simply turn off the required validators on all prevalue fields
Thank you, it is enough to know I was doing it right :-) In the meantime I shall immediately alert the v7 uCssClassNameDropdown user community to the issue !
Providing an optional configuration parameter to a property editor
I'm kind of in the process of moving uCssClassNameDropdown to Umbraco 7, such is the weight of popular demand: detailed here: http://www.tooorangey.co.uk/posts/u-css-class-name-dropdown-property-editor-for-umbraco-7/
I have an exclusion list configuration option, for people to specify classnames they want to exclude from the list, but can't be bothered to make the regex more complicated to unmatch it; so most of the time this field wil be blank, setting it to view 'textstring' it throws an error 'value cannot be empty' if it is left blank:
Just wondering if I was missing something obvious:to make the setting 'nullable'
{ label: "Exclusion list", description: "comma delimited list of styles to exclude", key: "excludeList", view: "textstring" }If you can, I'd suggest trying this with a nightly build and seeing if you still get the same issue. I saw some bugs in 7.0 with leaving certain properties blank, this may be a similar bug, and from what I saw at least some have been fixed in the latest builds.
Hope this helps,
David
that is odd, the view itself, doesn't contain any validation at all, you dont have any dublicate entries in that manifest? - Care to share it so I can reproduce?
Thanks, yes,
http://www.tooorangey.co.uk/media/uCssClassNameDropDown.zip
is a zip of the files in question
there is always the possibility I'm doing something monumentally stupid.
Alright, so it wasnt you who were doing something stupid, it was our pre-value validation.
So basically, if you add validation to any of the fields, this validation was triggered against all fields. I've already committed a fix for it, so tomorrow morning there will be a nightly build with this fix in, and its also included in 7.0.1 ofcourse.
If you want the fix now, you need to build from source (from the 7.0.1 branch) - or simply turn off the required validators on all prevalue fields
Thank you, it is enough to know I was doing it right :-) In the meantime I shall immediately alert the v7 uCssClassNameDropdown user community to the issue !
is working on a reply...