-
-
Notifications
You must be signed in to change notification settings - Fork 106
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
Fixed Internal Attributes #111 #112
Conversation
Signed-off-by: samtrion <[email protected]>
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.
This looks good. Thanks.
Can I get you to do a quick unit tests of this specific scenario. It should go in the relevant folder in the bunit.web.tests project?
Co-Authored-By: Egil Hansen <[email protected]>
Signed-off-by: samtrion <[email protected]>
Signed-off-by: samtrion <[email protected]>
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.
Thanks for the test. As I read the test though, it actually tests that MarkupMatches
correctly ignores the special Blazor attributes, and not that we correctly prefix all special Blazor attributes.
We do actually still render the attributes, so what you probably can do to write a test for this scenario, is to use a css query for the element with the click handler, and verify that it contains the attributes as expected, with the proper prefixed name. Makes sense?
Thanks again for your help.
Signed-off-by: samtrion <[email protected]>
Guess that should fit so far. |
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.
Looks good. thanks.
Signed-off-by: samtrion [email protected]