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.

Sign up for GitHub

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

Jump to bottom

bind-property-event syntax #10769

Closed
guardrex opened this issue Feb 2, 2019 — with docs.microsoft.com · 0 comments
Closed

bind-property-event syntax #10769

guardrex opened this issue Feb 2, 2019 — with docs.microsoft.com · 0 comments
Assignees
@ajaybhargavb
Labels
Blazor Pri1 High priority, do before Pri2 and Pri3 Source - Docs.ms Docs Customer feedback via GitHub Issue
Projects
Blazor.Docs
Milestone
Backlog

Comments

@guardrex docs.microsoft.com
Copy link
Collaborator

guardrex commented Feb 2, 2019

From @Andrzej-W at aspnet/Blazor.Docs#368 ...

Here dotnet/aspnetcore#5521 is a discussion about a bug in data binding. Notice the syntax: bind-value-oninput=@myField and a few other examples. It is not documented at all and should be added here: https://blazor.net/docs/components/index.html#data-binding

First, someone from Blazor team should tell us whether in the foreseeable future it will work as expected and what is really expected. Is this universal syntax in the form bind-property-event or only bind-value-event. It is probably designed only for HTML elements and not for user defined components. Which HTML elements?

  • input (what type? text, password, checkbox, etc., new HTML types: date, time, number, email, etc.)
  • textarea
  • select

cc: SteveSandersonMS

From @guardrex ...

Thanks @Andrzej-W ... I'll wait until we hear from SteveSandersonMS on the questions you asked. However, some quick testing should also be able to determine what's supported if I get to this before he responds. I might have some time next weekend to take a look at this issue.

From @Andrzej-W ...

@guardrex Quick testing in Blazor 0.7 is unfortunately not enough - usually you will get Error: System.InvalidCastException: Specified cast is not valid. (dotnet/aspnetcore#5521 (comment))

From @guardrex ...

Yes, I mean that it "isn't supported" if an error is thrown, so we wouldn't document anything for the current release that doesn't work.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@dotnet-bot dotnet-bot added the Source - Docs.ms Docs Customer feedback via GitHub Issue label Feb 2, 2019
@guardrex guardrex added this to To do in Blazor.Docs via automation Feb 2, 2019
@guardrex guardrex added this to the Backlog milestone Feb 2, 2019
@danroth27 danroth27 added Pri1 High priority, do before Pri2 and Pri3 and removed DT labels Feb 5, 2019
@guardrex guardrex moved this from Triage to P0/P1 - High Priority Work List in Blazor.Docs Feb 5, 2019
@ajaybhargavb ajaybhargavb self-assigned this Feb 26, 2019
@ajaybhargavb ajaybhargavb mentioned this issue Feb 27, 2019
Merged
@ajaybhargavb ajaybhargavb moved this from P0/P1 - High Priority Work List to P2 - Medium Priority Work List in Blazor.Docs Feb 28, 2019
Blazor.Docs automation moved this from P2 - Medium Priority Work List to Done Feb 28, 2019
Rick-Anderson pushed a commit that referenced this issue Feb 28, 2019
@ajaybhargavb @Rick-Anderson
Document bind-property-event syntax and add a note about lambda expre…
693c437 
…ssions (#11152)

Fixes #10769 and #10768
Rick-Anderson pushed a commit to dotnet/AspNetDocs that referenced this issue Mar 17, 2019
@Banani-Rath @Rick-Anderson
Docid_fix (#5)
24e58ac 
* Add a policy schemes doc (#11150)

* Create policyschemes.md

* Update policyschemes.md

* Update policyschemes.md

* Update policyschemes.md (#11154)

[Internal review URL](https://review.docs.microsoft.com/en-us/aspnet/core/security/authentication/policyschemes?view=aspnetcore-1.0&branch=pr-en-us-11154)

* Added note about deprecated features (#11098)

* Added note about deprecated these features

Added a note that the web performance and load testing tools in Visual Studio is deprecated and will be removed after VS 2019 as was announced here: https://docs.microsoft.com/en-us/visualstudio/releases/2019/release-notes-preview#test-tools

In the same note, a line was added about the load testing service in Azure DevOps closing in 2020 from the announcement here: https://devblogs.microsoft.com/devops/cloud-based-load-testing-service-eol/

* Update load-tests.md

* Update load-tests.md

* Fix glob pattern in .gitignore (#11165)

* Add async iterator sample to the SignalR streaming doc (#11140)

* Clarify default proxy addresses (#11167)

Fixes #10651

Approved on the issue by engineering.

* 2.2 example for AzureWebAppDiagnostics (#11169)

Fixes #11029 
[Internal review URL](https://review.docs.microsoft.com/en-us/aspnet/core/fundamentals/logging/index?view=aspnetcore-2.2&branch=pr-en-us-11169#logging-in-azure)

* Move youtube link (#11176)

* youtube link (#11177)

* youtube link (#11178)

* youtube link (#11179)

* youtube link (#11181)

* youtube link (#11183)

* youtube link (#11185)

* youtube link (#11186)

* youtube link (#11180)

* youtube link

* Update sql.md

* youtube link (#11188)

* Patch bookmarks (#11190)

Patch a few broken bookmarks.

* RP route and app conventions update (#11194)

Fixes #6801 

* Add example code for `IPageHandlerModelConvention` to the sample app (but it's not wired up to do anything really ... just shows how to implement it generally).
* Take sample app to 2.2.
* Drop the *Replace the default page app model provider* and sample code for it per instructions from engineering (see the issue).
* Take topic to 2.1+ (shed 2.0 content).
* XREF links (I really suspect that a VSC Extension could do 90% of the conversion work ... I should consider creating it.)

* Document bind-property-event syntax and add a note about lambda expressions (#11152)

Fixes dotnet/AspNetCore.Docs#10769 and dotnet/AspNetCore.Docs#10768

* updated referenced JS files (#11193)

`blazor.server|webassembly.js` are now `components.server|webassembly.js` as of ASP.NET Core 3.0 preview 2

* Updated namespace usage (#11191)

* Update BlazorLayoutComponent > LayoutComponentBase (#11189)

* Update BlazorLayoutComponent LayoutComponentBase (#11187)

* Update BlazorLayoutComponent > LayoutComponentBase (#11184)

* Update startup.md (#11200)

* Add Form Action Tag Helper docs (#11192)

- Utilized the `AnchorTagHelper` docs to consistenly describe the `asp-` attributes used to control how links get generated.
- Updated the built in TagHelper list doc to include the FormAction TagHelper.

#10593 
[Review URL](https://review.docs.microsoft.com/en-us/aspnet/core/mvc/views/working-with-forms?view=aspnetcore-2.2&branch=pr-en-us-11192#the-form-action-tag-helper)

* Update cicd.md (#11113)

Closes #11074

* Add more ANCM startup failures (#11155)

* Update logging to 2.2 (#11207)

Also convert inline code snippet to reference.

Fixes #11206 

[Internal review URL](https://review.docs.microsoft.com/en-us/aspnet/core/fundamentals/logging/index?view=aspnetcore-2.2&branch=pr-en-us-11207#azure-app-service-provider)
<!--
# Instructions

When creating a new PR, please reference the issue number if there is one:

Fixes #Issue_Number

The "Fixes #nnn" syntax in the PR description allows GitHub to automatically close the issue when this PR is merged.

NOTE: This is a comment; please type your descriptions above or below it.
-->

* Update Redis section of dist caching (#11160)

* Add snippet about how to configure OIDC options (#11182)

* Add snippet about how to configure OIDC options

* Update azure-ad-b2c.md

* Update aspnetcore/security/authentication/azure-ad-b2c.md

Co-Authored-By: HaoK <HaoK@users.noreply.github.com>

* Update aspnetcore/security/authentication/azure-ad-b2c.md

Co-Authored-By: HaoK <HaoK@users.noreply.github.com>

* Update azure-ad-b2c.md

* Update azure-ad-b2c.md

* Refactor code snippet

* More code snippet refactoring

* updating and removing aspnet/docs (aspnetcore)

* Update docfx.json (#3)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ajaybhargavb ajaybhargavb

Labels
Blazor Pri1 High priority, do before Pri2 and Pri3 Source - Docs.ms Docs Customer feedback via GitHub Issue
Projects
Blazor.Docs
Archived in project
Blazor.Docs
  
Done
Milestone
Backlog
Development

No branches or pull requests
4 participants
@ajaybhargavb @guardrex @danroth27 @dotnet-bot