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

Fix typos #2359

Merged
merged 1 commit into from
Sep 11, 2024
Merged

Fix typos #2359

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
4 changes: 2 additions & 2 deletions docs/guides/how-to/create-a-custom-field.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ Then we follow the steps below:
tracking interaction states etc.

> N.B. Make sure you never override other property getters than the one mentioned in this tutorial,
> because those properties will loose their reactivity (they won't be considered anymore in the
> because those properties will lose their reactivity (they won't be considered anymore in the
> update loop of LitElement).
> Whenever a .modelValue/.formattedValue/.serializedValue needs to be computed, use
> [parser/formatter/serializer](../../docs/../fundamentals/systems/form/formatting-and-parsing.md)
Expand Down Expand Up @@ -194,7 +194,7 @@ export const createAField = () => {
That was all!
Now that your .modelValue is connected your component is fully compatible with our form system

> Is your `.modelValue` still undefined? Please make sure you're `.value` is of type 'string'.
> Is your `.modelValue` still undefined? Please make sure your `.value` is of type 'string'.

Now you can enhance your slider by writing custom Validators for it or by
writing a parser to get a custom modelValue type.