Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allowing for user-defined string type in lexer/parser #1009

Merged
merged 1 commit into from
Mar 13, 2018
Merged

Allowing for user-defined string type in lexer/parser #1009

merged 1 commit into from
Mar 13, 2018

Conversation

nlohmann
Copy link
Owner

With #1006 we allowed for user-defined string types in the serializer. This PR also adds support for user-defined string types in the lexer and parser.

Thanks to @RalfBielig for noting.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 8557151 on user_string_parser into b56ac86 on develop.

@nlohmann nlohmann added this to the Release 3.1.2 milestone Mar 13, 2018
@nlohmann nlohmann self-assigned this Mar 13, 2018
@nlohmann nlohmann merged commit 919d1fe into develop Mar 13, 2018
@nlohmann nlohmann deleted the user_string_parser branch March 13, 2018 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@nlohmann nlohmann

Labels
None yet
Projects
None yet
Milestone
Release 3.1.2
Development

Successfully merging this pull request may close these issues.
2 participants
@nlohmann @coveralls