Skip to content

Conversation

@glennsarti
Copy link
Contributor

@glennsarti glennsarti commented Jun 27, 2020

Fixes #65

Previously the tokeniser always thought node names must a be a single string,
however they can also be regular expressions and the keyword default. And they
can be a list of these separate by commas. This commuit updates the node
regular expressions for all of these types of node names and adds tests for
these scenarios


Reminder

  • Added Tests

  • Ran npm run convert and committed the changes too

@glennsarti glennsarti added this to the 1.3.7 milestone Jun 27, 2020
@glennsarti glennsarti self-assigned this Jun 27, 2020
Previously the tokeniser always thought node names must a be a single string,
however they can also be regular expressions and the keyword default. And they
can be a list of these separate by commas.  This commuit updates the node
regular expressions for all of these types of node names and adds tests for
these scenarios
@glennsarti glennsarti changed the title WIP(GH-65) Node name tokeniser (GH-65) Tokenise Node names correctly Jun 28, 2020
@glennsarti glennsarti marked this pull request as ready for review June 28, 2020 05:54
@jpogran jpogran merged commit 57695b7 into puppetlabs:master Jun 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Node definition does not tokenise correctly for 'default'

2 participants