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

Allow Type CharSquence in 'parse*()' method instead of String #23

Closed
patrickfav opened this issue Aug 14, 2018 · 1 comment
Closed

Allow Type CharSquence in 'parse*()' method instead of String #23

patrickfav opened this issue Aug 14, 2018 · 1 comment
Assignees
@patrickfav
Labels
enhancement
Milestone
v0.8.0

Comments

@patrickfav
Copy link
Owner

It is best practice and more flexible to expect the interface of String, CharSequence als input of the parser methods. Note that it will break the BinaryToTextEncoding interface (although this should be easy to fix)
@patrickfav patrickfav added this to the v0.8.0 milestone Aug 14, 2018
@patrickfav patrickfav self-assigned this Aug 14, 2018
@patrickfav
Copy link
Owner Author

Fixed in 04e18dd

@patrickfav patrickfav changed the title Allow CharSquence in 'parse*()' method except for String Allow Type CharSquence in 'parse*()' method instead of String Aug 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@patrickfav patrickfav

Labels
enhancement
Projects
None yet
Milestone
v0.8.0
Development

No branches or pull requests
1 participant
@patrickfav