Split code into core and submodules for non-core code
See original GitHub issueGoing to move the following out of core:
json
rest/http
The resulting folder structure will be:
/
(README.md
,CHANGELOG.md
,LICENSE
)src/
(parent folder for all source)src/tornadofx2
(tornadofx2 core; root forpom.xml
)src/tornadofx2/src
(tornadofx2 core; code)src/tornadofx2-json
(json extensions; root forpom.xml
)src/tornadofx2-json/src
(json extensions; code)src/tornadofx2-rest
(rest extensions; root forpom.xml
)src/tornadofx2-rest/src
(rest extensions; code)docs/
root for documentation
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Divide Your Python Code Using Modules and Classes
Generally speaking, you want each class in a separate file, and that file to be named the same as the class.
Read more >How are golang sub-modules supposed to be expressed by ...
But I can't see a reliable way to split go modules into namespace and name without analyzing the module's git repo. And I'd...
Read more >Effectively Working with Git Submodules
So decided to split whole code-base into git submodules and setup separate repositories for each of the sub-systems.
Read more >Code Style Guide | Android Open Source Project
Code Style Guide ... The HIDL code style resembles C++ code in the Android framework, with 4-space indents and mixed-case filenames. Package ...
Read more >ROSE Compiler Framework/Source Code Repository
Risks and MitigationEdit · it is hard to make sure non-core repositories always work with the core ROSE repository; Or changes to the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If I can add my $0.02, I’m not a fan of the
/src/
directory. I prefer either having the different modules at root (very common, e.g. Spring)/tornadofx2-core/
(ortornadofx2-base
, I’m not a fan of justtornadofx2
)/tornadofx2-rest/
/tornadofx2-.../
/docs/
Or, if a directory is desired, use
/modules/
(less common, but not rare, e.g. JavaFX)./modules/tornadofx2-core/
/modules/tornadofx2-rest/
/modules/tornadofx2-.../
/docs/
I think the
/src/[module]/src/
construct is quite strange.how do you look at adding kotlin and kotlin DSL contacts to avoid problems with scopes.
I can do this.
Is it better to do this in the new
Github Projects
?