Replies: 1 comment 1 reply
-
@SlavaVedernikov in case you haven't seen this yet. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm finally getting some time to dig into C4InterFlow after creating my fork months ago. But something I'm noticing is that there's not really any guidance as a developer to getting started. Also noticing some full, hardcoded paths (like in the launchSettings.json) that make it difficult to just clone the repo and run it...at least from Visual Studio. Using things like well-known MSBuild properties/environment variables.
Also things like code convention preferred in the project so PR's are more about intent/features rather than code consistency. Stuff like .editorconfig/ReSharper shared project settings/etc.
Considering you've been solo on this for so long, would you be open to those sorts of PRs?
I have a bigger need for documenting my company's deployment infrastructure, so I wanted to see if I could start implementing Issue #62 but ran into those difficulties so far.
Beta Was this translation helpful? Give feedback.
All reactions