Skip to content
This repository has been archived by the owner on Feb 25, 2021. It is now read-only.

Remove old workaround @onclick and @bind #525

Merged
merged 1 commit into from
Apr 10, 2018
Merged

Commits on Apr 10, 2018

  1. Remove old workaround @OnClick and @Bind

    This change removes support for the old syntax used for event handlers
    and two-way binding.
    
    See the relevant issues for details on the new features and
    improvements:
    
    bind https://github.com/aspnet/Blazor/issues/409
    event handlers https://github.com/aspnet/Blazor/issues/503
    
    Along with this change we've removed a few additional things Blazor
    could do that aren't part of Razor's usual syntax.
    
    ----
    
    The features that was used to make something like:
    ```
    <button @OnClick(...) />
    ```
    
    is an expression that's embedded in a an element's attribute. This
    feature might be useful in the future if we want to support 'splatting'
    arbitrary attributes into a tag, but the runtime support for this isn't
    accessible outside the Blazor core.
    
    ----
    
    The features that implement:
    ```
    <button onclick=@{ } />
    ```
    
    have been removed in favor of a better design for lambdas, method group
    conversions and other things for event handler attributes.
    
    use `<button onclick=@(x => ...} />` instead.
    
    We think is a better approach in general, because we want the app
    developer to write and see the parameter list.
    
    ----
    
    Both syntactic features that have been removed have dedicated error
    messages in the compiler. If you're porting old code it should help you
    figure out what to do.
    rynowak authored and Ryan Nowak committed Apr 10, 2018
    Configuration menu
    Copy the full SHA
    cda57e7 View commit details
    Browse the repository at this point in the history