-
Notifications
You must be signed in to change notification settings - Fork 79
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
Rewrite in Java, drop Scala dependencies #159
base: master
Are you sure you want to change the base?
Conversation
7273222
to
506daa4
Compare
A non-required property can be non-nullable. It can either be omitted, or if specified must be non-null.
2b95da9
to
21163e3
Compare
Please consider this PR seriously. The Scala collection dependencies really hurt. |
Why is nobody merging this? |
@mbknor who is the active maintainer? |
@muliyul @kyale Thank you for the support. Expecting a project to switch languages and accept a rewrite pull request is a tall order. Feel free to just switch to my fork. It's on Maven, I've been updating it with features/fixes (see the master 1.1.2 branch), and will take PRs. Beside, this project brags in the README "Benefits: Simple implementation - Just one file" The file is 1500 lines. So idk what you can expect from the maintainer. |
Resolves #160 Tests pass. This has the same behavior as 1.0.39, with fix to #152.
Most of the changes are straight conversions from Scala to Java. Use of Option and endless
map
andforeach
has been eliminated in favor of simpleif(... != null)
. A few things were refactored such as moved into separate files, but not much. The Java code actually ended up being more concise and definitely a lot clearer than Scala.EDIT: I realized I should have made a separate branch with original groupId, etc. If there's interest, I'll recreate this PR.