If we need people to download a single dependency for the entire track, then we will typically describe this as part of the setup for the track (install the language environment, install the test library, download this thing that you'll need, etc).
Currently the ballerina directory structure looks like this:
One of the requirements that we enforce is that each directory in the exercises directory needs to be an exercise, and it needs to be self-contained.
For many languages this is simple, where you end up with something like this:
At other times, we need to account for a deeper directory tree, e.g.:
If we need people to download a single dependency for the entire track, then we will typically describe this as part of the setup for the track (install the language environment, install the test library, download this thing that you'll need, etc).
Currently the ballerina directory structure looks like this:
Would you walk me through what
.ballerina
andhello-world-service
andrun_ballerina_tests.sh
are for?