-
Notifications
You must be signed in to change notification settings - Fork 48
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
Net 9 and Update Deps #2251
base: main
Are you sure you want to change the base?
Net 9 and Update Deps #2251
Conversation
@@ -30,7 +30,7 @@ jobs: | |||
|
|||
build-and-test: | |||
if: github.event_name == 'push' || github.event.pull_request.draft == false | |||
uses: Nexus-Mods/NexusMods.App.Meta/.github/workflows/dotnet-build-and-test-with-osx.yaml@ae64a3be780a74e94b59ee463a413083013c8b0c | |||
uses: Nexus-Mods/NexusMods.App.Meta/.github/workflows/dotnet-build-and-test-with-osx.yaml@main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not using a pinned version of the workflows could cause issues.
Changes to the Meta repo that also require changes to the underlying repos would break CI during the mean time.
E.g. while the PR with the changes is being reviewed, Ci on all other PRs will break.
Just pointing it out, in case it others have opinions on this
src/Abstractions/NexusMods.Abstractions.MnemonicDB.Attributes/RelativePathAttribute.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a couple of more db attributes in the LoadOrder v1 pr #2248
There are going to be conflicts there as I also created new modes that use our local attributes, those will need updating as well
This PR conflicts with |
This PR doesn't conflict with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some duplicate attributes still exist and should be removed. The new optional values should also be implemented instead of just defaulting to calling .Value
where the status of the value is unclear. Use a try-get method or manual if-checks instead.
This PR conflicts with |
This PR does the following: