Project: A Topic Report You Can Explain

You’ve counted messages, kept the messages behind a count, and combined a topic check with an approved check. Now you’ll put those pieces together into one small report that answers a real request and that you can explain message by message.

By the end of this brief, you’ll have the report’s rule in words, a decision about unreviewed messages, and a plan for the two functions you’ll build in the next exercise.

Read the Request

Say a teammate asks you this:

How many messages about returns came in, and which ones are they?

Before any code, pin down what the answer counts. Each record is one message, not one customer. The records don’t say who wrote them, so your report counts messages and should say so.

The topic labels need a closer look, too. A label with the status "approved" has been reviewed. A "pending" label hasn’t, so it might still change. Here are four messages:

Locked learning resources

Join us and get access to thousands of tutorials and a community of expert JavaScript developers.

Unlock This Lesson

Already a member? Sign-In

Locked learning resources

The full lesson is for members only. Join us and get access to thousands of tutorials and a community of expert JavaScript developers.

Unlock This Lesson

Already a member? Sign-In

Become a Member to join the conversation.