Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Stacks API entries should be sorted to reflect priority #9821

Closed
mattchenderson opened this issue Jan 19, 2024 · 1 comment · Fixed by Azure/azure-functions-ux#7554
Closed

Stacks API entries should be sorted to reflect priority #9821

mattchenderson opened this issue Jan 19, 2024 · 1 comment · Fixed by Azure/azure-functions-ux#7554
Assignees
@mattchenderson
Labels
area: host-split cli-dependency

Comments

@mattchenderson
Copy link
Contributor

mattchenderson commented Jan 19, 2024 •
edited
Loading

Some tools use the ordering (after checking the default property, hopefully). Right now, .NET Framework 4.8 is first for .NET and can be selected by some tools. A separate Stacks API change will fix this, but we should also clean up the API in general.

We're also pursuing changes in the CLI to provide some related defenses, but best to have both: Azure/azure-cli#28224
@mattchenderson mattchenderson self-assigned this Jan 19, 2024
@mattchenderson mattchenderson transferred this issue from Azure/azure-functions-dotnet-worker Jan 19, 2024
@mattchenderson mattchenderson mentioned this issue Jan 26, 2024
Merged
@mattchenderson
Copy link
Contributor Author

Closing as this was addressed by the linked PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mattchenderson mattchenderson

Labels
area: host-split cli-dependency
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Reordering stacks for .NET in Functions mattchenderson/azure-functions-ux
1 participant
@mattchenderson