-
Notifications
You must be signed in to change notification settings - Fork 2
treewide: update project structure #17
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
base: main
Are you sure you want to change the base?
treewide: update project structure #17
Conversation
9b03e8e to
ba59845
Compare
ba59845 to
b39bbf0
Compare
c33bde4 to
93fc585
Compare
|
TODO: add this back, what is this? |
|
@anton-schieber I'll have a look at this PR tomorrow. Just wanted to let you know, what this project code is. This code is part of the solution file to define a virtual folder in the Solution Explorer of Visual Studio called "Solution Items". It just makes it easier to work with these files in Visual Studio as you normally don't see files on the solution level in the solution explorer. :)
|
|
Nvm. I reviewed it today, haha. First of all, thanks for contributing @anton-schieber! ❤️ I like the thought of having this project more organized on GitHub and I think the hierarchy is overall better. However, I already used the term Further, namespaces, packageIds and also assemblyNames should follow default conventions and the My recommended structure would be this: I really appreciate your effort and think this refactoring is a very good idea! 🙏 Resources: |
Splitting up the project into: - src - tests - samples - benchmarks This change was driven by that fact that viewing in github the project names cannot be read as they are too long.
93fc585 to
8bb91a9
Compare
|
Updated in line with your spec |
|
Merge this before anything else please, its a lot of work to have to resolve conflicts on something like this |


Splitting up the project into:
This change was driven by that fact that viewing in github the project names cannot be read as they are too long.