Skip to content

feat: add support for keyword mappers in custom mode JSON #11

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

pepijnve
Copy link

When the value for the token key of a rule is an object, this will now get converted to a keyword
mapper. The token object should contain the keys
map, defaultToken, ignoreCase, and splitChar

When the value for the `token` key of a rule is an
object, this will now get converted to a keyword
mapper. The token object should contain the keys
`map`, `defaultToken`, `ignoreCase`, and `splitChar`
@F0rce
Copy link
Owner

F0rce commented Apr 21, 2023

@pepijnve thanks for the PR. Just out of curiousity, do you think that it could be worth, if I update Ace to the latest version as well. The Ace Vaadin Webcomponent hasn’t received the love it used to get.

If so, I would work on in that weekend and merge on monday. Or would you need the changes faster, that I fully test out your changes, and create a seperate PR for upgrading Ace and switching to a Vite build ?

@pepijnve
Copy link
Author

If it's not too much work that would be nice.

There's no need to rush the mode changes.

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