* chore: rename APIs and Microservices to include "Backend" (#42515) * fix typo * fix typo * undo change * Corrected grammar mistake Corrected a grammar mistake by removing a comma. * change APIs and Microservices cert title * update title * Change APIs and Microservices certi title * Update translations.json * update title * feat(curriculum): rename apis and microservices cert * rename folder structure * rename certificate * rename learn Markdown * apis-and-microservices -> back-end-development-and-apis * update backend meta * update i18n langs and cypress test Co-authored-by: Shaun Hamilton <shauhami020@gmail.com> * fix: add development to front-end libraries (#42512) * fix: added-the-word-Development-to-front-end-libraries * fix/added-the-word-Development-to-front-end-libraries * fix/added-word-development-to-front-end-libraries-in-other-related-files * fix/added-the-word-Development-to-front-end-and-all-related-files * fix/removed-typos-from-last-commit-in-index.md * fix/reverted-changes-that-i-made-to-dependecies * fix/removed xvfg * fix/reverted changes that i made to package.json * remove unwanted changes * front-end-development-libraries changes * rename backend certSlug and README * update i18n folder names and keys * test: add legacy path redirect tests This uses serve.json from the client-config repo, since we currently use that in production * fix: create public dir before moving serve.json * fix: add missing script * refactor: collect redirect tests * test: convert to cy.location for stricter tests * rename certificate folder to 00-certificates * change crowdin config to recognise new certificates location * allow translations to be used Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com> * add forwards slashes to path redirects * fix cypress path tests again * plese cypress * fix: test different challenge Okay so I literally have no idea why this one particular challenge fails in Cypress Firefox ONLY. Tom and I paired and spun a full build instance and confirmed in Firefox the page loads and redirects as expected. Changing to another bootstrap challenge passes Cypress firefox locally. Absolutely boggled by this. AAAAAAAAAAAAAAA * fix: separate the test Okay apparently the test does not work unless we separate it into a different `it` statement. >:( >:( >:( >:( Co-authored-by: Sujal Gupta <55016909+heysujal@users.noreply.github.com> Co-authored-by: Noor Fakhry <65724923+NoorFakhry@users.noreply.github.com> Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com> Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com>
157 lines
3.9 KiB
Markdown
157 lines
3.9 KiB
Markdown
---
|
|
id: 5a24c314108439a4d4036147
|
|
title: Connect Redux to React
|
|
challengeType: 6
|
|
forumTopicId: 301426
|
|
dashedName: connect-redux-to-react
|
|
---
|
|
|
|
# --description--
|
|
|
|
Now that you've written both the `mapStateToProps()` and the `mapDispatchToProps()` functions, you can use them to map `state` and `dispatch` to the `props` of one of your React components. The `connect` method from React Redux can handle this task. This method takes two optional arguments, `mapStateToProps()` and `mapDispatchToProps()`. They are optional because you may have a component that only needs access to `state` but doesn't need to dispatch any actions, or vice versa.
|
|
|
|
To use this method, pass in the functions as arguments, and immediately call the result with your component. This syntax is a little unusual and looks like:
|
|
|
|
```js
|
|
connect(mapStateToProps, mapDispatchToProps)(MyComponent)
|
|
```
|
|
|
|
**Note:** If you want to omit one of the arguments to the `connect` method, you pass `null` in its place.
|
|
|
|
# --instructions--
|
|
|
|
The code editor has the `mapStateToProps()` and `mapDispatchToProps()` functions and a new React component called `Presentational`. Connect this component to Redux with the `connect` method from the `ReactRedux` global object, and call it immediately on the `Presentational` component. Assign the result to a new `const` called `ConnectedComponent` that represents the connected component. That's it, now you're connected to Redux! Try changing either of `connect`'s arguments to `null` and observe the test results.
|
|
|
|
# --hints--
|
|
|
|
The `Presentational` component should render.
|
|
|
|
```js
|
|
assert(
|
|
(function () {
|
|
const mockedComponent = Enzyme.mount(React.createElement(AppWrapper));
|
|
return mockedComponent.find('Presentational').length === 1;
|
|
})()
|
|
);
|
|
```
|
|
|
|
The `Presentational` component should receive a prop `messages` via `connect`.
|
|
|
|
```js
|
|
assert(
|
|
(function () {
|
|
const mockedComponent = Enzyme.mount(React.createElement(AppWrapper));
|
|
const props = mockedComponent.find('Presentational').props();
|
|
return props.messages === '__INITIAL__STATE__';
|
|
})()
|
|
);
|
|
```
|
|
|
|
The `Presentational` component should receive a prop `submitNewMessage` via `connect`.
|
|
|
|
```js
|
|
assert(
|
|
(function () {
|
|
const mockedComponent = Enzyme.mount(React.createElement(AppWrapper));
|
|
const props = mockedComponent.find('Presentational').props();
|
|
return typeof props.submitNewMessage === 'function';
|
|
})()
|
|
);
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --after-user-code--
|
|
|
|
```jsx
|
|
const store = Redux.createStore(
|
|
(state = '__INITIAL__STATE__', action) => state
|
|
);
|
|
class AppWrapper extends React.Component {
|
|
render() {
|
|
return (
|
|
<ReactRedux.Provider store = {store}>
|
|
<ConnectedComponent/>
|
|
</ReactRedux.Provider>
|
|
);
|
|
}
|
|
};
|
|
ReactDOM.render(<AppWrapper />, document.getElementById('root'))
|
|
```
|
|
|
|
## --seed-contents--
|
|
|
|
```jsx
|
|
const addMessage = (message) => {
|
|
return {
|
|
type: 'ADD',
|
|
message: message
|
|
}
|
|
};
|
|
|
|
const mapStateToProps = (state) => {
|
|
return {
|
|
messages: state
|
|
}
|
|
};
|
|
|
|
const mapDispatchToProps = (dispatch) => {
|
|
return {
|
|
submitNewMessage: (message) => {
|
|
dispatch(addMessage(message));
|
|
}
|
|
}
|
|
};
|
|
|
|
class Presentational extends React.Component {
|
|
constructor(props) {
|
|
super(props);
|
|
}
|
|
render() {
|
|
return <h3>This is a Presentational Component</h3>
|
|
}
|
|
};
|
|
|
|
const connect = ReactRedux.connect;
|
|
// Change code below this line
|
|
```
|
|
|
|
# --solutions--
|
|
|
|
```jsx
|
|
const addMessage = (message) => {
|
|
return {
|
|
type: 'ADD',
|
|
message: message
|
|
}
|
|
};
|
|
|
|
const mapStateToProps = (state) => {
|
|
return {
|
|
messages: state
|
|
}
|
|
};
|
|
|
|
const mapDispatchToProps = (dispatch) => {
|
|
return {
|
|
submitNewMessage: (message) => {
|
|
dispatch(addMessage(message));
|
|
}
|
|
}
|
|
};
|
|
|
|
class Presentational extends React.Component {
|
|
constructor(props) {
|
|
super(props);
|
|
}
|
|
render() {
|
|
return <h3>This is a Presentational Component</h3>
|
|
}
|
|
};
|
|
|
|
const connect = ReactRedux.connect;
|
|
// Change code below this line
|
|
|
|
const ConnectedComponent = connect(mapStateToProps, mapDispatchToProps)(Presentational);
|
|
```
|