I have a question, have you been in a situation wh...

# random

[andylamax]

I have a question, have you been in a situation where you have two libraries, one to be used publicly, and the other one to be used only internally by the company/team you are working with.

Let me give an example.
Taking a bike sharing service for example.
The public side (offered to be used by the public), just has an interface to retrieve available bikes, and book one dynamically, usable if a programmer would like to integrate bike sharing services in their applications.

The private side (only to be used internally by the team), depends on the public sdk but adds more functionality like managing UI states, handling forms directly, e.t.c

Question is, how would you go naming these two libraries??

At the moment, we have something similar to
bike-core (for public)
bike-full (for internal)

Very not cool.

Planning to switch to
bike-public
bike-private

But I cringe having to see maven coordinates like "io.testbike public1.0.0" and "io.test.bike-private:1.0.0" in my gradle script

What would your suggestion be?

[Fleshgrinder]

bike-api (public) and just bike (private) would be my choice.

[andylamax]

Thanks for the suggestions

made me thing about

bike-api (public)
bike-sdk (private)