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.

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

new java libraries #121

Open
vtitov opened this issue Mar 26, 2019 · 3 comments
Open

new java libraries #121

vtitov opened this issue Mar 26, 2019 · 3 comments

Comments

@vtitov
Copy link

vtitov commented Mar 26, 2019

To whom it may concern,

I created a pair java libraries for robotframework:
Reflection based dynamic wrapper around java-faker: https://github.com/vtitov/faker-javalib
Static wrappers around java-uuid methods: https://github.com/vtitov/robotframework-java-uuid

There is a question about artifacts naming and releasing. Can I use org.robotframework groupId? or should I use my own (e.g. com.github.vtitov)?

Another question is about documentation. How detailed should it be at this early stage of development, taking into account that these are wrappers around java methods: documented in case of uuid or intuitively clear for faker.

Regards,
Valentin

@pekkaklarck
Copy link
Member

I don't know how groupIds are typically handled. Do others, for example @jussimalinen or @Hi-Fi, have insight about this?

Documentation should be so good that others can use the libraries without needing to bother you with questions all the time. Referring to external documentation is generally fine.

@Hi-Fi
Copy link
Contributor

Hi-Fi commented Mar 27, 2019

I think that it's best to use groupId that refers to source code repo. So in this case com.github.vitov.

I think that keyords that are offered by library should be documented in a level, that user knows what those do and if there's something else that needs to be known without checking external documentation or code. External documentation can be referred, but basically user should...

  • understand what keyword does by it's name
  • understand the arguments and return values by keyword documentation
  • get deeper understanding of the library by external documentation.

E.g. in SeleniumLibrary (both Java and Python) documentation doesn't explain how Selenium works, but only what user needs to know to use keywords efficiently (

@vtitov
Copy link
Author

vtitov commented Mar 27, 2019

Juho, Pekka,

Thank you for suggestions.
I'll make some corrections in projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants