-
Notifications
You must be signed in to change notification settings - Fork 94
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
Support expanding <param1><param2>
in inherited family names
#5537
Support expanding <param1><param2>
in inherited family names
#5537
Conversation
95ad6d9
to
11b4cca
Compare
I think it needs to be documented now that's it's becoming officially supported syntax. All examples in the docs will (presumably) be using the original syntax. |
Coming back to this after a couple of days I can't believe I said this! |
Converted to draft until I've:
|
I had a look at using the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've unresolved some of Oliver's comments which have not been addressed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've noticed that <x>foo<y>
ends up like _x1foo_y1
, though I imagine this is a low priority issue
This includes the following, not previously permitted pattern: `familyname<foo><bar>` and `family<foo>name<bar>`.
cb47f4f
to
4abf220
Compare
5ad9503
to
4abf220
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Closes #5118
The form
FAM<foo,bar>
is already supported in graph strings and[runtime][task]inherit
, while the functionally equivalentFAM<foo><bar>
is only supported in graph strings. This PR adds full support for the latterCheck List
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
(andconda-environment.yml
if present).CHANGES.md
entry included if this is a change that can affect usersIf this is a bug fix, PR should be raised against the relevantN/A?.?.x
branch.