@@ -121,7 +121,7 @@ ref: connect-to-your-mongodb-realm-app
121
121
content : |
122
122
To get the app working with your backend, you first need to instantiate the
123
123
Realm app. The Realm app is the interface to the MongoDB Realm backend.
124
- Navigate to the getRealmApp.js file and complete the ``getRealmApp()``
124
+ Navigate to the `` getRealmApp.js`` file and complete the ``getRealmApp()``
125
125
function implementation:
126
126
127
127
.. literalinclude:: /tutorial/generated/code/final/getRealmApp.codeblock.get-realm-app.js
@@ -134,8 +134,8 @@ content: |
134
134
title : Implement the AuthProvider
135
135
ref : implement-the-auth-provider
136
136
content : |
137
- Navigate to providers/AuthProvider.js. In this file, and in the
138
- providers/TasksProvider.js file that we will complete a bit later, we use
137
+ Navigate to `` providers/AuthProvider.js`` . In this file, and in the
138
+ `` providers/TasksProvider.js`` file that we will complete a bit later, we use
139
139
React :reactjs:`Context <docs/context.html>` and :reactjs:`hooks
140
140
<docs/hooks-overview.html>` to implement a data provider pattern. Don't worry
141
141
if you aren't too familiar with these constructs yet. The basic idea is as
@@ -179,7 +179,7 @@ content: |
179
179
realm may be empty when first opened. Add an observer to the collection of
180
180
users in that realm in order to watch for the user object first appearing as
181
181
well as any changes to the its Project memberships. When a user object is
182
- available, read its memberOf field to populate the available Project data for
182
+ available, read its `` memberOf`` field to populate the available Project data for
183
183
any descendant of the provider:
184
184
185
185
.. literalinclude:: /tutorial/generated/code/final/AuthProvider.codeblock.open-user-realm.js
@@ -192,7 +192,7 @@ content: |
192
192
.. literalinclude:: /tutorial/generated/code/final/AuthProvider.codeblock.user-realm-cleanup.js
193
193
:language: javascript
194
194
195
- Check out the App.js, view/WelcomeView.js, and view/ProjectView.js files to
195
+ Check out the `` App.js``, `` view/WelcomeView.js`` , and `` view/ProjectView.js`` files to
196
196
see how they use the AuthProvider's signIn, signUp, and signOut functions and
197
197
user data via the ``useAuth()`` hook function. The ProjectView also uses the
198
198
Project data to populate the list of Projects available to the logged-in user.
@@ -203,7 +203,7 @@ title: Define the Task Schema
203
203
ref : define-the-task-schema
204
204
content : |
205
205
In order to work with Task objects in the Realm Database, we need to define
206
- their schema. Navigate to the schemas.js file to complete the Task class's
206
+ their schema. Navigate to the `` schemas.js`` file to complete the Task class's
207
207
schema definition:
208
208
209
209
.. literalinclude:: /tutorial/generated/code/final/schemas.codeblock.react-native-task-schema.js
@@ -253,31 +253,31 @@ content: |
253
253
.. literalinclude:: /tutorial/generated/code/final/TasksProvider.codeblock.delete-task.js
254
254
:language: javascript
255
255
256
- Check out the views/TasksView.js and components/TaskItem.js files to see how
256
+ Check out the `` views/TasksView.js`` and `` components/TaskItem.js`` files to see how
257
257
they use the provider's task data and functionality via the ``useTasks()``
258
258
hook function.
259
259
---
260
260
title : Implement Team Management
261
261
ref : implement-team-management
262
262
content : |
263
263
A user can add other users to their team, which allows them to view, edit, and
264
- delete Tasks on the user's Project. The ManageTeam component implements this
264
+ delete Tasks on the user's Project. The `` ManageTeam`` component implements this
265
265
functionality by calling a few Realm functions on the backend that we defined
266
266
earlier.
267
267
268
- Navigate to components/ManageTeam.js. First, we need to fetch the list of
268
+ Navigate to `` components/ManageTeam.js`` . First, we need to fetch the list of
269
269
current team members:
270
270
271
271
.. literalinclude:: /tutorial/generated/code/final/ManageTeam.codeblock.get-team.js
272
272
:language: javascript
273
273
274
- Next, call the addTeamMember function on the backend to implement add team
274
+ Next, call the `` addTeamMember`` function on the backend to implement add team
275
275
member functionality:
276
276
277
277
.. literalinclude:: /tutorial/generated/code/final/ManageTeam.codeblock.add-team-member.js
278
278
:language: javascript
279
279
280
- Finally, call the removeTeamMember function on the backend to implement remove
280
+ Finally, call the `` removeTeamMember`` function on the backend to implement remove
281
281
team member functionality:
282
282
283
283
.. literalinclude:: /tutorial/generated/code/final/ManageTeam.codeblock.remove-team-member.js
0 commit comments