Add check to prevent storage layer importing domain layer or domain layer importing controller layer
See original GitHub issueThis is a tracking issue for the check to prevent storage layer, core/storage
importing domain layer, core/domain
or domain layer, core/domain
importing controller layer, core/controllers
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Domain layer | Android Developers
The domain layer is responsible for encapsulating complex business logic, or simple business logic that is reused by multiple ViewModels. This ...
Read more >Implementing Domain Driven Design - ABP Documentation
This is a practical guide for implementing the Domain Driven Design (DDD). While the implementation details rely on the ABP Framework ...
Read more >Domain-driven Design (DDD): File Structure
Infrastructure Layer: Is how data that is initially held by in the domain's entities (memory) is persisted in databases or another ...
Read more >Security+ Domain 3.0 Implementation Flashcards - Quizlet
A network administrator is importing a list of certificates from an online ... It uses Secure Sockets Layer/Transport Layer Security (SSL/TLS) certificates.
Read more >Multiple ways of defining Clean Architecture layers
We can check if imports of each class defined in the domain layer and flag and error if there are imortas that point...
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
I am fine either way. The only requirement is that nothing is merged to develop “halfway”, and I think both alternatives satisfy that.
Thanks for checking!
@seanlip Ah okay then I’ll wait for @apb7 to review the already existing PR to verify my current approach since the same approach will do the second part too. Also I think it would be easier for him to review the subsequent changes for the same part fix which he reviewed earlier. And then when the existing PR gets an LGTM I’ll drop the other half of the fix 'coz then the class would be in develop, so the later fix will be less messy once I pull it. Thanks!