-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Blazor API Review: Microsoft.AspNetCore.Components.Web #12339
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
Conversation
2757bcb
to
0677885
Compare
@SteveSandersonMS @pranavkm this is ready for review.
I can't reproduce the problem with newer VS bits than the public preview. I think the issue is that we look for |
dd733b2
to
4c29eb0
Compare
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.
It's excellent to see it's possible to move all this stuff out into .Web
. It feels like the "core" vs "web" layering is actually making sense now.
Without blocking this PR, let's also discuss whether we want to API-review all the eventargs types and strip them down to the set that actually makes sense in Blazor today. Quite a number of them can't be used for anything practical, as per my comments here.
4c29eb0
to
1fe7c76
Compare
Also undid the use of ref assemblies in our tests. This is kinda wierd and breaks dev inner-loop.
1fe7c76
to
3c4dd4c
Compare
See: #12329