Closed Chang-CH closed 6 months ago
Perhaps to futureproof this somewhat, should we have a different folder under src
for packages like these? @martin-henz @RichDom2185
Perhaps to futureproof this somewhat, should we have a different folder under
src
for packages like these? @martin-henz @RichDom2185
In js-slang, we have src/alt-langs
, and scm-slang
is a submodule there:
js-slang/src/alt-langs/scheme/scm-slang/...
so how about this:
modules/src/alt-langs/java/java-packages/src/...json
(edited above: java-standard-packages => java-packages. Reason: The naming scheme already provides for enough structure. "Non-standard" packages would fit into java-packages by just using appropriate qualified names.)
Perhaps to futureproof this somewhat, should we have a different folder under
src
for packages like these? @martin-henz @RichDom2185In js-slang, we have
src/alt-langs
, andscm-slang
is a submodule there:js-slang/src/alt-langs/scheme/scm-slang/...
so how about this:modules/src/alt-langs/java/java-packages/src/...json
(edited above: java-standard-packages => java-packages. Reason: The naming scheme already provides for enough structure. "Non-standard" packages would fit into java-packages by just using appropriate qualified names.)
OK, at the moment @Chang-CH has:
[submodule "src/java/java-packages"]
path = src/java/java-packages
This seems reasonable.
Description
Includes java-packages as submodule.
It exports an object of type
{[key: string]: string}
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Checklist: