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.

Sign up for GitHub

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

Jump to bottom

Architecture: should Interfaces have their own namespace? #47

Open
lhaze opened this issue Feb 2, 2019 · 1 comment
Open

Architecture: should Interfaces have their own namespace? #47

lhaze opened this issue Feb 2, 2019 · 1 comment
Assignees
@jakos
Labels
architecture Discussions about Principles and Assumptions of the Design help wanted question
Projects
Devops & project managment
Milestone
0.2

Comments

@lhaze
Copy link
Collaborator

lhaze commented Feb 2, 2019

It's a code layout question. Each interface have an owner on its own. But should they have an independent namespace to secure from circular imports? Could circular imports be a problem at all? Or should interfaces be closer to their owners?
@lhaze lhaze added help wanted modification architecture Discussions about Principles and Assumptions of the Design labels Feb 2, 2019
@lhaze lhaze added this to To do in Devops & project managment via automation Feb 2, 2019
@lhaze lhaze added this to the 0.1 milestone Feb 2, 2019
@lhaze lhaze assigned lhaze and jakos and unassigned lhaze Feb 2, 2019
@lhaze
Copy link
Collaborator Author

lhaze commented Feb 2, 2019

@jakos, would you like to state your opinion?

@lhaze lhaze modified the milestones: 0.1, 0.2 Dec 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jakos jakos

Labels
architecture Discussions about Principles and Assumptions of the Design help wanted question
Projects
Devops & project managment
  
To do
Milestone
0.2
Development

No branches or pull requests
2 participants
@jakos @lhaze