Closed CodyEngel closed 3 years ago
If you have questions about implementing feel free to ask here. Also don't forget to ask if you can pick up the issue and I can assign it to you.
Hi @CodyEngel can I take this one?
Oh, and since we are implementing based on java-faker, the library doesn't support semanticVersion
as in faker-ruby.
(https://github.com/DiUS/java-faker/blob/master/src/main/java/com/github/javafaker/App.java)
Should I implement all the other properties?
Hey @Caps-Looking feel free to pick this one up. When it comes to the versioning I was thinking it'd make sense to just generate that on our own using Random to generate the major, minor, and patch.
Today we are using java-faker
for a lot of the data generation but we will be breaking away from it shortly after the 1.0.0 release to start working on Kotlin Native support. Because of that I am okay with not using java faker if it doesn't support something that faker-ruby does and it's easy enough to implement.
Add app, which includes
name
,version
,author
, andsemanticVersion
. This should also include options to change the version's major/minor/patch values as well as being able to say if a library is early release or stable.