Name type #53
Name type #53
Conversation
|
@lukaspie, the test should not be failed. I see this is weird. In my local setup, if I run the test separately it does not fail, but it fails when I run it all together. |
| @@ -65,6 +66,7 @@ | |||
| "required", | |||
| "deprecated", | |||
| "units", | |||
| "nameType", | |||
There was a problem hiding this comment.
nameType is now twice in this tuple
| def check_for_proper_nameType(name, nameType, error_location): | ||
| """Check for proper nameType. | ||
|
|
||
| Name with all upper case letters should have nameType as `any` or `specific`. |
There was a problem hiding this comment.
It is specified, not specific!
|
|
||
| Name with all upper case letters should have nameType as `any` or `specific`. | ||
| Name with all lower case letters should have nameType as `specific`. | ||
| Name with uper case or lower case letters should have nameType as `spcific` or `partial`. |
There was a problem hiding this comment.
In principle, you can put nameType=any also for all lower cases or partially variadic names. You shouldn't do this, but technically, nothing prevents me from writing fieldFIELD, nameType=any and then replacing that by some_other_name. Or even my_field, nameType=any and replacing that by yet_another_name.
nameType="any" really means any, including all lower case parts
|
@RubelMozumder let's close this PR as this is now already handled. |
docordim. It should be and end leaf in yaml and nxdl.