-
Notifications
You must be signed in to change notification settings - Fork 134
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
Add Dotnet Isolated runtime specific dependencies and cleanup durableUtils
#3597
Conversation
durableUtils
src/utils/durableUtils.ts
Outdated
// Seems that the package arrives out-dated and needs to be updated to at least 2.9.1; | ||
// otherwise, error appears when running with sql backend | ||
if (!isDotnetIsolated) { | ||
packageNames.push(dotnetLtsDfBasePackage); |
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 100% sure if this is the best way to handle this; let me know if anyone has opinions on if this should be handled differently.
@@ -111,19 +113,9 @@ export namespace durableUtils { | |||
// eslint-disable-next-line @typescript-eslint/no-unsafe-assignment, @typescript-eslint/no-explicit-any, @typescript-eslint/no-unsafe-member-access | |||
let packageReferences = result?.['Project']?.['ItemGroup']?.[0]?.PackageReference ?? []; |
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.
Unrelated to this PR, but there is a bug here if the package references are split into multiple item groups since we're only using the first item group. I can fix this in a separate PR.
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.
Ahh good catch! It should probably loop through the 'ItemGroup'[] and check for the 'PackageReference' instead
Add .NET Isolated runtime specific dependencies, specifically for
Netherite
andMSSQL
storage types.Partially addresses the error message shown in #3566.