hakowork/vide
3
0
Fork 0
mirror of https://github.com/centau/vide.git synced 2026-08-20 14:41:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix typos

Browse source
This commit is contained in:
Aaron Smith 2023-09-21 19:14:55 +01:00
parent 62716a074d
commit 3c45defeac
5 changed files with 7 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/api/reactivity-utility.md
View file

@ -60,7 +60,7 @@ scope.
## read() ## read()
Utility used to read a value that is either a primitive or a source. Sources Utility used to read a value that is either a primitive or a source. Sources
read can still be tracked inside a reactive-scope. read can still be tracked inside a reactive scope.
- **Type** - **Type**

2
docs/tut/crash-course/4-source.md
View file

@ -1,4 +1,4 @@
# Source # Sources
*Sources* in Vide are special objects that store a single value. They are the *Sources* in Vide are special objects that store a single value. They are the
core of reactivity in Vide. Each source represents a source of data, and they core of reactivity in Vide. Each source represents a source of data, and they

2
docs/tut/crash-course/6-stateful-component.md
View file

@ -1,4 +1,4 @@
# Stateful Component # Stateful Components
A stateful component is a component that stores and displays some data. A stateful component is a component that stores and displays some data.

5
docs/tut/crash-course/7-property-binding.md
View file

@ -3,7 +3,8 @@
Explicitly creating effects to update properties can become verbose when there Explicitly creating effects to update properties can become verbose when there
are a lot of properties to update. Vide provides a way to *implicitly* create are a lot of properties to update. Vide provides a way to *implicitly* create
an effect to update properties on source update. This is also known as an effect to update properties on source update. This is also known as
*property binding*, as a property is binded to reflect some data. *property binding*, since changes to a source will automatically update the
property.
```lua ```lua
local create = vide.create local create = vide.create
@ -29,7 +30,7 @@ Instead of explicitly creating an effect, assigning a (non-event) property
a function will implicitly create a side-effect to update that property anytime a function will implicitly create a side-effect to update that property anytime
a dependent source is updated. a dependent source is updated.
Just like effects, the function is ran immediately in a reactive-scope to set Just like effects, the function is ran immediately in a reactive scope to set
the property initially and determine what sources are being depended on. the property initially and determine what sources are being depended on.
This allows you as the programmer to not need to manually update UI as the state This allows you as the programmer to not need to manually update UI as the state

2
docs/tut/crash-course/8-cleanup.md
View file

@ -43,6 +43,6 @@ covered next.
On a related note: the reason why `mount()` is used to create your app, is so On a related note: the reason why `mount()` is used to create your app, is so
that any top-level components that need to be cleaned up, can be cleaned up that any top-level components that need to be cleaned up, can be cleaned up
when the app is later unmounted, since `mount()` runs in a reactive-scope to when the app is later unmounted, since `mount()` runs in a reactive scope to
track `cleanup()` calls. Vide's entire reactive system is independent from the track `cleanup()` calls. Vide's entire reactive system is independent from the
life-time of instances; instances are just a side-effect of the reactive system. life-time of instances; instances are just a side-effect of the reactive system.