Standard Go Project Layout
-
Updated
Sep 10, 2020 - Makefile
The new npm style require syntax works by emiting modules that alias the namespace like this
(rule
(with-stdout-to FooCliPesyModules.re
(run echo "module AliasedDep = DepNamespace;\
\nmodule AliasedDep2 = Dep2Namespace;")))
If users, especially experienced ones, know the namespace of the library beforehand and the use same,
"imports": [Add a description, image, and links to the project-template topic page so that developers can more easily learn about it.
To associate your repository with the project-template topic, visit your repo's landing page and select "manage topics."
Now that Cloud Manager supports Java 11 and lets you configure it using the toolchains plugin
https://docs.adobe.com/content/help/en/experience-manager-cloud-service/onboarding/getting-access/creating-aem-application-project.html#using-java-11
It would be nice if the archetypes takes Java version as a user input and configures the toolchains plugin out of the box.