-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Inheritted group combo params #1838
base: dev-3.x
Are you sure you want to change the base?
Conversation
…ng is specified This fixes a regression caused by yui#1832.
CLA is valid! |
I've added tests for combine, and comboSep, but I wasn't sure how best to test that maxURLLength is applied differently within groups. |
comboBase = group.comboBase; | ||
comboSep = group.comboSep; | ||
maxURLLength = group.maxURLLength; | ||
if (typeof group.comboBase === 'string') { |
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.
Do we care about comboBase: ''
?
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.
Why wouldn't we? It should be possible to either specify a comboBase for a group, or to use the inheritted one. There are reasons you may want to do so, largely developer related admittedly.
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 don't have a personal stance in this case. But should we stick to backwards compatibility (''
being falsy)?
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.
guys, let's stick to the previous behavior, there is not need to change that behavior now.
This is based on the fix for #1837