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

[Docs] Mention conflicting components workarounds #5457

Open
stsrki opened this issue Apr 11, 2024 · 2 comments
Open

[Docs] Mention conflicting components workarounds #5457

stsrki opened this issue Apr 11, 2024 · 2 comments
Assignees
Labels
Type: Feature ⚙ Request or idea for a new feature.
Projects
Milestone

Comments

@stsrki
Copy link
Collaborator

stsrki commented Apr 11, 2024

Some component names might conflict with the native Blazor components. Like ValidationSummary. We need to mention the workarounds in the docs:

  • define full namespace <Blazorise.ValidationSummary>
  • disable global namespaces(is possible)
@stsrki stsrki added the Type: Feature ⚙ Request or idea for a new feature. label Apr 11, 2024
@stsrki stsrki added this to the 1.5 support milestone Apr 11, 2024
@stsrki stsrki self-assigned this Apr 11, 2024
@stsrki stsrki added this to 🔙 Backlog in Support via automation Apr 11, 2024
@mrpmorris
Copy link

If the user is migrating an existing app with lots of Microsoft form components, then this might be worth trying

  1. Add this to _Imports.razor
    @using MSForms = Microsoft.AspNetCore.Components.Forms
  2. Prefix the existing ValidationSummary components with MSForms.
  3. Now the app should compile again
  4. As they migrate each form, remove the MSForms. prefix

@stsrki
Copy link
Collaborator Author

stsrki commented Apr 12, 2024

@mrpmorris thanks for the suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature ⚙ Request or idea for a new feature.
Projects
Support
  
🔙 Backlog
Development

No branches or pull requests

2 participants