* Add new APIs to ComponentShim
* Add new APIs to ComponentsApi
* Add EventCallback metadata
* Add discovery of EventCallback properties
* Errata for Runtime APIs
* Add ability to use EventCallback as parameter
* Add support for bind to component
* Use EventCallback for bind-... to elements
* Use EventCallback<T> for event handlers
\n\nCommit migrated from a0b6bc0e52
- Added a step to full fidelity verification that does a `LocateOwner` at every source location. If we find a `null` owner we build a snippet with a detailed response to enable us to diagnose the problem.
Addresses aspnet/AspNetCoredotnet/aspnetcore-tooling#7718
\n\nCommit migrated from 08587a30fd
The changes here make event dispatching (including bind) more
user-friendly by avoiding the need for manual calls to StateHasChnaged.
We also introduce a new type `EventCallback` (and `EventCallback<T>`).
This is a new primitive that is like a super-powered version of a
delegate. When writing a component that accepts delegates as parameters,
consider using `EventCallback` for the following reasons:
- Allows consumer to pass a variety of different delegate signatures
- Does proper event dispatching and error handling
Using `EventCallback` will eliminate most of the remaining cases where a
manual `StateHasChanged` is required when components are passing content
and delegates to each other.
`EventCallback` is inherently async for the reason that this is really
the only way to provide correct error handling.
-----
The fix for this will be two-phase by first creating a set of APIs that
can be targeted by the compiler that has the desired behaviour and then
updating the compiler to target this new infrastructure.
* DefaultObjectPool left unchanged (expect access modifiers) + manual inlining ob scan-methods
* DisposableObjectPool made internal and it handles Return self, thus keeping the DefaultObjectPool fast
\n\nCommit migrated from a7dc496507
Changes:
* add entry for Mono.WebAssembly.Interop to Version.Details.xml
* Update code check to ensure all veriables in the 'automated' section are accounted for in Version.Details.xml
- Basic endpoint routing support to for SignalR hubs, ConnectionHandler and IConnectionBuilder endpoints
- Updated all functional tests and samples to use it
- Added all attributes as metadata from Hubs and ConnectionHandlers
- Added a test to verify client is rejected if auth is ineffective
* Update CONTRIBUTING.md
* Remove 2/3 please per MS style guide:
* *Avoid **please** except in situations where the customer is asked to do something inconvenient or the application or site is to blame for the situation.*
* The last please meets that bar.
* Add AspNetCore repo
* Remove double blank lines
* Edit
* Update CONTRIBUTING.md
* Update CONTRIBUTING.md
Ryan Brandenburg
Pranav K
Ryan Nowak
N. Taylor Mullen
Mikael Mengistu
Nate McMaster
TimTim
Steve Sanderson
Ben Adams
James Newton-King
Chris R
Justin Kotalik
Nate McMaster
Stephen Halter
David Fowler
Günther Foidl
Hao Kung
Pavel Krymets
Rick Anderson
Doug Bunting
Nikita Potapenko
Ajay Bhargav Baaskaran
Doug Bunting