-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After grace period, emit code with warnings #383
Conversation
fae8f07
to
1b63973
Compare
🧪 Details on macOS Unix 14.6.1✅ ThisAssemblyTests.ScribanTests.CanRenderModel 🧪 Details on Ubuntu 22.04.4 LTS✅ ThisAssemblyTests.ScribanTests.CanRenderModel 🧪 Details on Microsoft Windows 10.0.20348✅ ThisAssemblyTests.ScribanTests.CanRenderModel from dotnet-retest v0.6.3 on .NET 8.0.8 with 💜 |
b0a5220
to
d4ccfb8
Compare
It was made quite clear that (some?) folks would rather just disable our friendly warning rather than sponsor. So we'll instead just make sponsorship mandatory. See #352 (comment) I worked hard to accomodate very flexible options for sponsoring, and this project ain't maintaining itself. It's fine if folks use something else. I made this initially just for myself, and I'm glad it's been useful for others. We also add remarks to the emitted APIs during the grace period, so it's not surprising they turn to warnings later.
d4ccfb8
to
a5337d8
Compare
It was made quite clear that (some?) folks would rather just disable our friendly warning rather than sponsor. So we'll instead just make sponsorship mandatory.
See #352 (comment)
I worked hard to accomodate very flexible options for sponsoring, and this project ain't maintaining itself. It's fine if folks use something else. I made this initially just for myself, and I'm glad it's been useful for others.
TODO: pending updating AssemblyInfo and Strings to use the same approach (those don't leverage Constants like the others).