-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Avoid non-Git constants conflict, update root comment #415
Conversation
As presently defined, if a custom constant in user's project had a naming conflict (i.e. `Root` or `Url`), the item metadata in the editorconfig/options would be mixed up, since it uses the item spec for that. By using the full area name, we avoid that, and switch instead to the custom root feature of using `Root=.` instead. We also take advantage of the new custom root summary comment to better reflect the nature of the provided constants.
🧪 Details on macOS Unix 14.6.1✅ ThisAssemblyTests.ScribanTests.CanRenderModel 🧪 Details on Ubuntu 22.04.5 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 💜 |
As presently defined, if a custom constant in user's project had a naming conflict (i.e.
Root
orUrl
), the item metadata in the editorconfig/options would be mixed up, since it uses the item spec for that.By using the full area name, we avoid that, and switch instead to the custom root feature of using
Root=.
instead.We also take advantage of the new custom root summary comment to better reflect the nature of the provided constants.