Contributing
Guidelines for contributing to this project.
Pull requests have some guidelines before being approved.
Code Guidelines
Any new addition of a variable must include
finalStatic-abuse:
staticshould only be used if a class requires a helper method, such as merging strings or parsing a string to an object. There is no other reason to use static.Any new addition of a method must include:
Annotations: If a method returns something, mark it as either
@NotNullor@Nullabledepending on the outcome.Documentation: Explain what this method does, what it returns, what it MAY throw, what params are needed.
Parameters: Parameters will need the
@NotNullor@Nullableannotation, if the parameter is a primitive you must usefinal.
You cannot "optimize" a method / change internal code unless it is stated that you can make a PR to clean it up, there is very few points of this within the Wrapper, so only use contributions for new features and follow the guidelines.
Java is not C#
When talking about "Java is not C#", we are talking about curly braces & method/variable names.
Bad:
Good:
No curly braces in one-line returns
Bad:
Good:
Invokation of a method
When invoking a method and the method depends on another method in the class, you must always use this.
Bad:
Good:
Re-use of variables
Bad:
Good:
Nesting
Bad:
Good:
Last updated
Was this helpful?