-
Notifications
You must be signed in to change notification settings - Fork 11
Split repo into language specific examples #20
Comments
@hajoeichler are we considering this or not? |
Well, it works now and we put effort into the current setup. So I would keep it in one repo. |
The problem I see is that more and more samples will come and the build is kind of configured only for java. If we split the repos in my opinion we will have faster, dedicated and independent builds instead of a big gigantic one... |
My impression is that the problem is not the build but the fact that many (most) of the hello world examples are much too "frameworkey". IMHO a Hello World Example should not require library dependencies, should not have to be built if not in a strictly compiled language (e.g. the iOS example). I paid painfully and finally made a simple "dumpapi.groovy" script the actual helloworld for groovy instead of launching a mico-webserver. e.g.: Both our Java and Scala Helloworlds would not need to be compiled via a huge framework like sbt. Michael told me that you can just run a Scala file as a script. In other words: we should stay in the tradition of "Programming Language Hello Worlds", not "Framework Hello Worlds". For Frameworks we have real SDKs or example Projects in separate repositories. PS: I know that this would mean to dump and delete the "iOS" Helloworld and just post a Swift Class. |
@nkuehn agree but more examples are always better then less. Its nice to have simple and more advanced example as @emmenko provided here Also i still think that its user friendlier to have own repo for each hello world example. If i google for "sphere php" i would like to see dedicated repo for that and expect it to contain only PHP relevant stuff. |
@butenkor right, but if you google for "sphere php" you must find the PHP SDK and not just some hello world example. Just that we now have to develop the new PHP SDK :-) |
Java example is now located here: https://github.com/sphereio/sphere-hello-api-java |
It would be better to have an own repo for each
hello-api-*
language, to also have own dedicated travis builds.The text was updated successfully, but these errors were encountered: