Fix @bind-value to @bind-Value in Razor Component snippets #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The Blazor input component snippets were generating incorrect
@bind-valuesyntax (with lowercase 'v'), which causes errors in Blazor applications. Blazor expects@bind-Valuewith a capital 'V' for form input components.Solution
Updated the following snippets in
snippets/components.jsonto use the correct@bind-Valuesyntax:bitext- InputText componentbitextarea- InputTextArea componentbinumber- InputNumber componentbicheck- InputCheckbox componentbidate- InputDate componentThe
biselect(InputSelect) snippet already had the correct syntax and was not modified.Example
Before:
After:
This ensures all generated Blazor input component snippets use the correct binding syntax that matches the framework's expectations.
Also bumped the package version from 1.5.1 to 1.5.2 as per CONTRIBUTING.md guidelines.
Fixes the issue reported in #[issue_number]
Original prompt
Fixes #5
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.