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

Expanded Parser method argument support #844

Merged
merged 5 commits into from Sep 30, 2023
Merged

Expanded Parser method argument support #844

merged 5 commits into from Sep 30, 2023

Conversation

lhazlewood
Copy link
Contributor

Closes #328

- Ensured Parser worked with CharSequence, InputStream and Reader, not just String
- Changed Deserializer#deserialize(InputStream) to deserialize(Reader)
- JwtParser now extends from Parser to support these additional methods.

@lhazlewood
- Ensured Parser worked with CharSequence, InputStream and Reader, no…
12abcae 
…t just String

- Changed Deserializer#deserialize(InputStream) to deserialize(Reader)
@lhazlewood
Closes #328
0653123 
- Ensured Parser worked with CharSequence, InputStream and Reader, not just String
- Changed Deserializer#deserialize(InputStream) to deserialize(Reader)
- JwtParser now extends from Parser to support these additional methods.
@lhazlewood lhazlewood added this to the 0.12.0 milestone Sep 30, 2023
@lhazlewood lhazlewood self-assigned this Sep 30, 2023
@lhazlewood lhazlewood merged commit 05717d0 into master Sep 30, 2023
24 checks passed
@lhazlewood lhazlewood deleted the parsers branch September 30, 2023 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@lhazlewood lhazlewood

Labels
None yet
Projects
None yet
Milestone
0.12.0
Development

Successfully merging this pull request may close these issues.

JwtParser to parse CharSequence instead of String?
1 participant
@lhazlewood