Skip to content

Conversation

@sylwekb
Copy link

@sylwekb sylwekb commented Nov 2, 2018

  • Make sure you are merging your commits to master branch.
  • Add some descriptions and refer relative issues for you PR.
  • DO NOT include files inside lib directory.

@sylwekb
Copy link
Author

sylwekb commented Nov 2, 2018

Actually that would break other modifiers... closing for now

@sylwekb sylwekb closed this Nov 2, 2018
.replace(/^'/, '')
.replace(/'$/, '')
.replace(/:([\w-]+)=?([\w-]+)?/g, (m, key, value) => {
.replace(/:([\w-]+)=?([\w-]+)?/, (m, key, value) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is for extracting all possible configs. In the case of headings, we have only one at the moment.

I guess a better solution would be only match strings at the end. We may need to introduce a delimiter for determining where the starting point of configs is.

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.

2 participants