Skip to content

Commit 0eb4b14

Browse files
committed
fix missing pic
1 parent b75dc34 commit 0eb4b14

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

src/content/6/en/part6a.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,17 +11,17 @@ So far, we have followed the state management conventions recommended by React.
1111

1212
### Flux-architecture
1313

14-
Already years ago Facebook developed the [Flux]()- architecture to make state management of React apps easier. In Flux, the state is separated from the React components and into its own <i>stores</i>.
14+
Already years ago Facebook developed the [Flux](https://facebook.github.io/flux/docs/in-depth-overview/)-architecture to make state management of React apps easier. In Flux, the state is separated from the React components and into its own <i>stores</i>.
1515
State in the store is not changed directly, but with different <i>actions</i>.
1616

1717
When an action changes the state of the store, the views are rerendered:
1818

19-
![diagram action->dispatcher->store->view]()
19+
![diagram action->dispatcher->store->view](../../images/6/flux1.png)
2020

2121
If some action on the application, for example pushing a button, causes the need to change the state, the change is made with an action.
2222
This causes re-rendering the view again:
2323

24-
![same diagram as above but with action looping back]()
24+
![same diagram as above but with action looping back](../../images/6/flux2.png)
2525

2626
Flux offers a standard way for how and where the application's state is kept and how it is modified.
2727

src/content/6/fi/osa6a.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,15 +11,15 @@ Olemme noudattaneet sovelluksen tilan hallinnassa Reactin suosittelemaa käytän
1111

1212
### Flux-arkkitehtuuri
1313

14-
Facebook kehitti jo Reactin historian varhaisvaiheissa tilan hallinnan ongelmia helpottamaan [Flux](https://facebook.github.io/flux/docs/in-depth-overview)-arkkitehtuurin. Fluxissa sovelluksen tilan hallinta erotetaan kokonaan Reactin komponenttien ulkopuolisiin varastoihin eli <i>storeihin</i>. Storessa olevaa tilaa ei muuteta suoraan, vaan tapahtumien eli <i>actionien</i> avulla.
14+
Facebook kehitti jo Reactin historian varhaisvaiheissa tilan hallinnan ongelmia helpottamaan [Flux]((https://facebook.github.io/flux/docs/in-depth-overview/)-arkkitehtuurin. Fluxissa sovelluksen tilan hallinta erotetaan kokonaan Reactin komponenttien ulkopuolisiin varastoihin eli <i>storeihin</i>. Storessa olevaa tilaa ei muuteta suoraan, vaan tapahtumien eli <i>actionien</i> avulla.
1515

1616
Kun action muuttaa storen tilaa, renderöidään näkymät uudelleen:
1717

18-
![Action -> Dispatcher -> Store -> View](https://facebook.github.io/flux/img/overview/flux-simple-f8-diagram-1300w.png)
18+
![Action -> Dispatcher -> Store -> View](../../images/6/flux1.png)
1919

2020
Jos sovelluksen käyttö (esim. napin painaminen) aiheuttaa tarpeen tilan muutokseen, tehdään muutos actionin avulla. Tämä taas aiheuttaa uuden näytön renderöitymisen:
2121

22-
![Action -> Dispatcher -> Store -> View -> Action -> Dispatcher -> View](https://facebook.github.io/flux/img/overview/flux-simple-f8-diagram-with-client-action-1300w.png)
22+
![Action -> Dispatcher -> Store -> View -> Action -> Dispatcher -> View](../../images/6/flux2.png)
2323

2424
Flux tarjoaa siis standardin tavan sille miten ja missä sovelluksen tila pidetään sekä tavalle tehdä tilaan muutoksia.
2525

src/content/images/6/flux1.png

92.2 KB
Loading

src/content/images/6/flux2.png

116 KB
Loading

0 commit comments

Comments
 (0)