-
-
Notifications
You must be signed in to change notification settings - Fork 23
Comparing changes
Open a pull request
base repository: devlooped/ThisAssembly
base: e55548b
head repository: devlooped/ThisAssembly
compare: ed2f092
- 12 commits
- 16 files changed
- 2 contributors
Commits on Sep 30, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 91afce4 - Browse repository at this point
Copy the full SHA 91afce4View commit details -
Configuration menu - View commit details
-
Copy full SHA for ca18b8f - Browse repository at this point
Copy the full SHA ca18b8fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 8e97cfb - Browse repository at this point
Copy the full SHA 8e97cfbView commit details -
Configuration menu - View commit details
-
Copy full SHA for 66f2cdf - Browse repository at this point
Copy the full SHA 66f2cdfView commit details -
Configuration menu - View commit details
-
Copy full SHA for f39f692 - Browse repository at this point
Copy the full SHA f39f692View commit details -
Simplify VSIX package manifest sample
No need to showcase the xmlns attributes
Configuration menu - View commit details
-
Copy full SHA for 7a96c32 - Browse repository at this point
Copy the full SHA 7a96c32View commit details -
Configuration menu - View commit details
-
Copy full SHA for c04f7e8 - Browse repository at this point
Copy the full SHA c04f7e8View commit details -
Allow constants to define custom root comment summary
Since now most specific packages just extend and project @(Constant) items, they effectively are all "constants", and the comment on the root class used to be "Provides access project-defined constants.". This no longer is the case for the following: - Metadata: exposes project-defined AssemblyMetadata, not "constants" - AssemblyInfo: exposes [Assembly*] attributes - Git: build-time source repo information, not even project constants - Vsix: manifest values, again, not even project values. We should therefore allow a new metadata beside the `Root` attribute we added to allow custom roots: `RootComment`. Since each constant is emitted as a standalone file, we would have duplication, but we want to keep this approach for performance reasons. We default to the old comment if none is specified. Example of a custom constant with a custom root and its comment: ```xml <Constant Include="Foo.Bar" Value="Baz" Comment="A Bar value" Root="." RootComment="All the foos!" /> ```
Configuration menu - View commit details
-
Copy full SHA for 9558384 - Browse repository at this point
Copy the full SHA 9558384View commit details -
Avoid non-Git constants conflict, update root comment
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.
Configuration menu - View commit details
-
Copy full SHA for d604382 - Browse repository at this point
Copy the full SHA d604382View commit details -
Provide custom Vsix class summary
This reflects better where the values are coming from.
Configuration menu - View commit details
-
Copy full SHA for a8824f9 - Browse repository at this point
Copy the full SHA a8824f9View commit details -
Provide custom AssemblyInfo class summary
To better reflect the source of the values
Configuration menu - View commit details
-
Copy full SHA for 275e62f - Browse repository at this point
Copy the full SHA 275e62fView commit details -
Provide custom Metadata class summary
Note where the values come from in this package.
Configuration menu - View commit details
-
Copy full SHA for ed2f092 - Browse repository at this point
Copy the full SHA ed2f092View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff e55548b...ed2f092