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.

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

Revise RenderTreeBuilderAnalyzer requirement to force "literal" sequence parameters #42756

Open
1 task done
Youssef1313 opened this issue Jul 16, 2022 · 3 comments
Open
1 task done
Labels
analyzer Indicates an issue which is related to analyzer experience area-blazor Includes: Blazor, Razor Components
Milestone

Comments

@Youssef1313
Copy link
Member

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

The analyzer requires syntactically LiteralExpressionSyntax, I think this can be relaxed to just a compile-time constant, whether it's a constant field, a constant local, or a literal.

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

@javiercn javiercn added area-blazor Includes: Blazor, Razor Components analyzer Indicates an issue which is related to analyzer experience labels Jul 17, 2022
@javiercn javiercn added this to the Backlog milestone Jul 17, 2022
@ghost
Copy link

ghost commented Jul 17, 2022

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@mkArtakMSFT mkArtakMSFT modified the milestones: Backlog, BlazorPlanning Nov 5, 2023
@MackinnonBuck
Copy link
Member

@Youssef1313 Could you describe a scenario where you'd want to use a constant field or local constant instead of a literal?

@MackinnonBuck MackinnonBuck modified the milestones: Planning: WebUI, Backlog Dec 5, 2023
@ghost
Copy link

ghost commented Dec 5, 2023

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyzer Indicates an issue which is related to analyzer experience area-blazor Includes: Blazor, Razor Components
Projects
None yet
Development

No branches or pull requests

4 participants