E51: Digits, Part 3 (Contacts Collection)

For this experience, you will create the Contacts collection, seed it with data on startup, and access it in the List Contacts page. When finished, the page will look like this:

Notice that the UI hasn’t changed, but one less contact is shown when logged in as john@foo.com, since he only owns two of the three contacts.

Prelude

First, I suggest you watch my screencast before trying this WOD for the first time. I have not been able to find suitable resources for you to read prior to doing this WOD to cover all the Meteor concepts I will cover. So, it’s best for you to watch the solution one time through to orient yourself.

Second, be sure to review the chapters of the Meteor Guide listed in the Readings section, particularly the ones on Collections and Publications.

Merge your list-contacts branch into main

At the conclusion of the last WOD, your List Contacts Page mockup was in a branch called list-contacts-page-1 (and list-contacts-page-2).

Quit meteor if it is running.

Now switch to the main branch in GitHub Desktop, and merge one of your list contacts branches into it. Push your main branch to GitHub after the merge completes.

Start meteor using meteor npm run start, and check http://localhost:3000 (and the console) to ensure that the merge worked correctly.

The WOD

Now you’re ready to do this practice WOD. There are two rounds to this WOD, each timed individually.

Pedagogy Alert! You might be tempted to do this WOD by stepping through the video frame by frame and copying what I do. That is very dangerous: you will simply trick yourself into thinking you've learned the material, but you've actually only learned how to copy and paste what I do. The way to learn the material is to watch the screencast, then try to do the WOD without looking at it. If you get stuck, then stop, watch the video, and start over from the beginning. If you follow this approach, then it may take you a little longer to finish the assignment, but when you get succeed, you'll actually knnow how to do the task on your own.

Round 1

Start your timer.

1. Create a branch to hold your work.

Create a branch called contacts-collection-1 using GitHub Desktop, and publish this branch to GitHub.

If necessary, start up your application using meteor npm run start. Check to see that it’s running at http://localhost:3000. Take a look at the console to be sure there are no errors.

Pro Tip: run your app within the Terminal window in IntelliJ, and keep Chrome Dev Tools open during development. Install Meteor Dev Tools Enhanced if you haven’t already.

2. Define the Contacts collection.

Make a copy of the app/imports/api/stuff directory, and call it contact. Rename Stuff.js to Contacts.js.

In api/contact/Contacts.js, rename the collection to Contacts. Update the schema to provide fields firstName, lastName, address, image, description, and owner. All fields are Strings.

3. Update settings.development.json with sample contact data.

Using the contacts field in ListContacts.jsx as your guide, edit settings.development.json with a new field called defaultContacts that contains an array of sample data. Note: You must add a ‘owner’ field: use john@foo.com for two of the data items and admin@foo.com for the other.

4. Load sample contact data on startup.

Edit app/imports/startup/server/Mongo.js to load the sample contact data on startup if there are no documents in the Contacts collection.

5. Check your work so far.

Stop Meteor, invoke meteor reset to clear the database, then meteor npm run start. You should see the following printed out:

[~/github/philipmjohnson/digits/app]-> meteor reset
Project reset.
[~/github/philipmjohnson/digits/app]-> meteor npm run start

> meteor-application-template-react@ start /Users/philipjohnson/github/philipmjohnson/digits/app
> meteor --no-release-check --settings ../config/settings.development.json

[[[[[ ~/github/philipmjohnson/digits/app ]]]]]

=> Started proxy.
=> Started HMR server.
=> Started MongoDB.
I20180302-17:07:09.981(-10)? Creating the default user(s)
I20180302-17:07:10.007(-10)?   Creating user admin@foo.com.
I20180302-17:07:10.008(-10)?   Creating user john@foo.com.
I20180302-17:07:10.008(-10)? Creating default data.
I20180302-17:07:10.008(-10)?   Adding: Basket (john@foo.com)
I20180302-17:07:10.008(-10)?   Adding: Bicycle (john@foo.com)
I20180302-17:07:10.008(-10)?   Adding: Banana (admin@foo.com)
I20180302-17:07:10.008(-10)?   Adding: Boogie Board (admin@foo.com)
I20180302-17:07:10.009(-10)? Creating default contacts.
I20180302-17:07:10.009(-10)?   Adding: Johnson (john@foo.com)
I20180302-17:07:10.009(-10)?   Adding: Casanova (john@foo.com)
I20180302-17:07:10.009(-10)?   Adding: Binsted (admin@foo.com)
I20180302-17:07:10.009(-10)? Monti APM: completed instrumenting the app
=> Started your app.

=> App running at: http://localhost:3000/

This console output indicates that three contacts are created by default.

6. Publish the Contact data to clients.

Edit app/imports/startup/server/Publications.js to define a publication called Contacts.userPublicationName that publishes all of the contacts associated with the currently logged in user. Also create a Contacts.adminPublicationName publication to publish all the Contacts when the logged in user is the Admin.

7. Edit ListContacts to display data from the Contacts collection.

Edit ListContacts.jsx to remove the contacts field, subscribe to the Contacts publication, and map through contacts to generate the displayed contacts.

When you are finished, the List Contacts page for john@foo.com should look like this:

If you log out and log in as admin@foo.com, then the page should look like this:

As you can see, only the Contacts associated with the logged in user are displayed.

8. Implement the admin page

Make a copy of app/imports/ui/components/Contact.jsx called ContactAdmin.jsx. Change the component name to ContactAdmin. After the Card.Text add a footer with the class “blockquote-footer” containing the owner.
Make a copy of app/imports/ui/pages/ListContacts.jsx called ListContactsAdmin.jsx. Change the component name to ListContactsAdmin. Subscribe to Contacts.adminPublicationName rather than Contacts.userPublicationName. Map to ContactAdmin, not Contact. Change the title of the page to “List Contacts (Admin)”
In app/imports/ui/layouts/App.jsx, make the admin route go to ListContactsAdmin rather than ListStuffAdmin.

When you’ve finished, the Admin page should look like this:

Notice that the Admin can subscribe to a publication that gets all the Contacts regardless of who the owner is. Only users with the Admin role can do that.

9. Check to make sure there are no ESLint errors

As a last step, run meteor npm run lint to ensure that there are no ESLint errors anywhere in your application.

10. Commit your finished work.

When your page renders correctly,

control-c to stop Meteor.
Stop your timer and note your time.
Commit and push your contacts-collection-1 branch to GitHub with the message ‘contacts collection finished in NN minutes.’, where NN is the number of minutes it took you to do it according to your timer.

Round 2

To ensure that you understand this material, you must do this WOD a second time.

Switch back to the main branch. This will revert your local repo to its state just before the start of this WOD.

Create a new branch called contacts-collection-2.

Go through the WOD again. When you’re done, commit and push your contacts-collection-2 branch to GitHub with the message ‘contacts collection finished in NN minutes.’, where NN is the number of minutes it took you to do it according to your timer.

Your TA will check whether both branches are in GitHub.

Rx: <30 min Av: 30-35 min Sd: 35-40 min DNF: 40+ min

Demonstration

Here’s a screencast of me working through this problem. You can watch this prior to attempting it for the first time yourself.

Submission instructions

By the time and date indicated on the Schedule page, submit this assignment via Laulima.

You must grant read access to this repo to the TA for your section. To do this:

Retrieve your repository in a browser, then click on “Settings”. Depending upon the GitHub UI you are provided, you’ll then click on either “Collaborators” or “Manage Access”. Let us know if you can’t find either of these.
Search for “acatarinaoaraujo”, then click “Add collaborator”.

Your submission should contain:

A link to each branch of the GitHub repository created as a result of your latest attempt at this practice WOD. Make sure you include the complete URLs for all branches so that I can click on them in my mailer. Note: the final commit for these branches must have been made before the submission time and date, otherwise you will not receive credit for this assignment.

You will receive full credit for this practice WOD as long as you have attempted it the required number of times and submitted the email with all required data before the due date. Your code does not have to run perfectly for you to receive full credit. However, if you do not repeat each practice WOD until you can finish it successfully in at least AV time, you are unlikely to do well on the in-class WOD. To reduce the stress associated with this course, I recommend that you repeat each practice WOD as many times as necessary to achieve at least AV before its due date.