You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a fantastic tool, but I think one of the main barriers to wider adoption is the (perhaps unwarranted) fear of applying code re-writing across an entire codebase.
I think there would be a much larger/faster adoption of the tool if there was an additional set of attribute that allowed per-class or member opt-in vs. opt-out.
This could come in the form of an assembly level opt-out attribute (like the NoLinqRewriteAttribute at the assembly level), and an opt-in attribute at the class/member level (like a 'ApplyLinqRewriteAttribute').
I would be happy to create an initial PR if this was something that sounds acceptable.
The text was updated successfully, but these errors were encountered:
Great. I'll put together a PR. One question, do you have the Shaman.Runtime.NoLinqRewriteAttribute exposed anywhere already, or is that left up to the implementer? It doesn't appear to be in the repo.
This is a fantastic tool, but I think one of the main barriers to wider adoption is the (perhaps unwarranted) fear of applying code re-writing across an entire codebase.
I think there would be a much larger/faster adoption of the tool if there was an additional set of attribute that allowed per-class or member opt-in vs. opt-out.
This could come in the form of an assembly level opt-out attribute (like the NoLinqRewriteAttribute at the assembly level), and an opt-in attribute at the class/member level (like a 'ApplyLinqRewriteAttribute').
I would be happy to create an initial PR if this was something that sounds acceptable.
The text was updated successfully, but these errors were encountered: