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

Create a guidance for developers on how to start contributing to C4InterFlow #100

Open
SlavaVedernikov opened this issue Sep 13, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers

Comments

@SlavaVedernikov
Copy link
Owner

See #97 (comment)

TBD

@SlavaVedernikov SlavaVedernikov added documentation Improvements or additions to documentation good first issue Good for newcomers labels Sep 13, 2024
sevans-tcp pushed a commit to kopelli/C4InterFlow that referenced this issue Sep 16, 2024
Because Visual Studio stores the startup project in the user settings for a solution, when one is not set up yet -- such as after cloning the repo locally and running it for the first time -- it will default to the first project listed in the .sln file.
Since the CLI project is the end goal, switching up the order in the file to fit this behavior.

SlavaVedernikov#100
sevans-tcp pushed a commit to kopelli/C4InterFlow that referenced this issue Sep 16, 2024
It makes sense that the default execution should be against something that already exists in the repository.
Tried to make this match the 'draw-diagrams.bat' file in the directory, the output doesn't quite match any more.

SlavaVedernikov#100
sevans-tcp pushed a commit to kopelli/C4InterFlow that referenced this issue Sep 16, 2024
sevans-tcp pushed a commit to kopelli/C4InterFlow that referenced this issue Sep 16, 2024
This helps bring in a consistent set of settings that apply to the codebase as a whole, and do not depend on the individual's IDE settings.
This also helps be explicit on what analyzer settings are enforced vs. what ones the project does not wish to adhere to.

SlavaVedernikov#100
sevans-tcp pushed a commit to kopelli/C4InterFlow that referenced this issue Sep 17, 2024
Because Visual Studio stores the startup project in the user settings for a solution, when one is not set up yet -- such as after cloning the repo locally and running it for the first time -- it will default to the first project listed in the .sln file.
Since the CLI project is the end goal, switching up the order in the file to fit this behavior.

SlavaVedernikov#100
sevans-tcp pushed a commit to kopelli/C4InterFlow that referenced this issue Sep 17, 2024
It makes sense that the default execution should be against something that already exists in the repository.
Tried to make this match the 'draw-diagrams.bat' file in the directory, the output doesn't quite match any more.

SlavaVedernikov#100
sevans-tcp pushed a commit to kopelli/C4InterFlow that referenced this issue Sep 17, 2024
sevans-tcp pushed a commit to kopelli/C4InterFlow that referenced this issue Sep 17, 2024
This helps bring in a consistent set of settings that apply to the codebase as a whole, and do not depend on the individual's IDE settings.
This also helps be explicit on what analyzer settings are enforced vs. what ones the project does not wish to adhere to.

SlavaVedernikov#100
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant