Skip to content

Fix typos in the LiveComponent readme #103

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

Merged
merged 1 commit into from
Jun 18, 2021
Merged

Fix typos in the LiveComponent readme #103

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/LiveComponent/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -525,7 +525,7 @@ class RandomNumberComponent implements LiveComponentInterface

When you trigger an action, a POST request is sent that contains
a `X-CSRF-TOKEN` header. This header is automatically populated
and violated. In other words... you get CSRF protection without
and validated. In other words... you get CSRF protection without
any work.

Your only job is to make sure that the CSRF component is installed:
Expand Down Expand Up @@ -674,7 +674,7 @@ a `post_form` component that we will create next:
```

Ok: time to build that `post_form` component! The Live Components package
come with a special trait - `ComponentWithFormTrait` - to make it easy to
comes with a special trait - `ComponentWithFormTrait` - to make it easy to
deal with forms:

```php
Expand Down Expand Up @@ -1051,7 +1051,7 @@ class EditUserComponent implements LiveComponentInterface
Be sure to add the `@Assert\IsValid` to any property where you want
the object on that property to also be validated.

Tahnks to this setup, the component will now be automatically validated
Thanks to this setup, the component will now be automatically validated
on each render, but in a smart way: a property will only be validated
once its "model" has been updated on the frontend. The system keeps track
of which models have been updated (e.g. `data-action="live#update"`)
Expand Down