Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code Modularisation Support #71

Open
jbee opened this issue Feb 6, 2019 · 0 comments
Open

Code Modularisation Support #71

jbee opened this issue Feb 6, 2019 · 0 comments

Comments

@jbee
Copy link
Owner

jbee commented Feb 6, 2019

Add something that allows to check for proper code modularisation. Instead of using modules on build level (e.g. maven) to avoid unwanted code dependencies packages in a single build module could be used as long as some tool tells us when "illegal" references are created. The DI container could help with this to some extend. While it cannot check and enforce universal class level isolation it can make sure container managed instances are not used where they should not be used. In connection with vanilla java visibility modifiers this allows to write code that is hardened against "spaghetti" code effect.

@jbee jbee self-assigned this Feb 6, 2019
@jbee jbee removed their assignment Jan 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant