Anything I should know before contributing? #8
JaceTheGrayOne
started this conversation in
General
Replies: 0 comments
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.
-
I was initially going to write something like this from the ground up in WPF or C# but then I found this and its foundation is pretty much exactly what I planned on doing anyway.
For having been built with AI this is a pretty impressive project. That being said, there are a number of design inconsistencies and obvious "AI" pitfalls which is to be expected and most people wouldn't bother dealing with unless they were over-neurotic.
I thought about forking this and re-designing it to include some improved functionality, strip out some of the stuff I wouldn't need, and overhaul the design but fortunately/Unfortunately I am overly neurotic and am willing to go through and fix all the nitpicky stuff like inconsistent UI element reactivity, interactive vs non-interactive element presentation, and non-functional elements as well as propose improved functionality like true first class parity syncing between the UI element based entry and raw code displays.
So, having said all that... is there anything in particular I should know prior to submitting PRs, any particular patterns or expectations you have for code/commenting or anything else like that?
Beta Was this translation helpful? Give feedback.
All reactions