I am once again in a position where #dotnet support for monkey-patching would make my life so much easier.
@khalidabuhakmeh I'm working in the TypeScript / Node / React world now, and we have used monkey-patching a few times to work around some sticky problems.
@khalidabuhakmeh there was "Fody" that could do it at IL level iirc
@khalidabuhakmeh like type classes? :)
@range_marten No, I mean: “Hey there’s a bug in this method of an otherwise great OSS project, I wish I could patch it locally.”
@khalidabuhakmeh This is one of the reasons I have been proposing source code sharing rather than binary sharing :)
@range_marten The issue with source code sharing is it bloats your repos and makes it difficult to determine what you changed and what the author changed.
@khalidabuhakmeh There are no silver bullets ofc but at least you _can_ change the source code as opposed to more complex decompile, change, compile :)
@khalidabuhakmeh and lack of tooling doesn't really help. Git submodules are not granular enough to work as a distribution mechanism. Libs are not designed for source code sharing and so on :)
@khalidabuhakmeh If we switched back to using ClearCase perhaps it would work better! When is the GIT replacement finally arriving?
@khalidabuhakmeh @range_marten I may be remembering things incorrectly, but didn’t Hornget have a decent solution to this?