Architecture & Conventions #4
ghost1face
started this conversation in
General
Replies: 2 comments 6 replies
-
|
I'm moving forward with generating tests to adhere to the spec. Once we have this we can start developing and validating the current open pull request and accepting future changes |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey all,
@0xZunia and community, I'm opening this discussion to establish some architectural guidelines and conventions. This is not the end-all be all, I'm open for feedback.
Initially I'd like to start with a few basics and open up some questions based on the different implementations I've seen:
Repo Structure:
src/ToonFormatlocation of formatter library to be distributed as a public Nuget package under the reserved nametests/ToonFormat.Testslocation of all testsConventions:
dotnet new editorconfigconfiguration so there's no personal preferences - focus is on functionalityFramework Support:
Dependencies:
Versioning:
A few questions I want to pose are:
System.Text.Json? I'd prefer not to have dependencies if we can help it, since consumers may have specific versions the rest of their code may depend on.To start I will be taking on the unit tests to ensure all changes adhere to the spec, this will make pulling in and validating changes a much smoother process
Beta Was this translation helpful? Give feedback.
All reactions