Create a guidance for developers on how to start contributing to C4InterFlow #100
Labels
Comments
SlavaVedernikov
added
documentation
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
sevans-tcp
pushed a commit
to kopelli/C4InterFlow
that referenced
this issue
Sep 25, 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 25, 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 25, 2024
sevans-tcp
pushed a commit
to kopelli/C4InterFlow
that referenced
this issue
Sep 25, 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
See #97 (comment)
The text was updated successfully, but these errors were encountered: