cm-core-team / cm-core Goto Github PK

Create some formatting and linting configs so that code styles are consistent everywhere.

Find a way to set environment variables in the integration/e2e test workflow for GitHub actions. These will contain sample secrets.

Research: to set private keys etc., find a way to store a .env.secret or the like. So that we can do e2e tests.

For integration tests, we could (whenever we use API keys, secrets, etc.) mock external API requests. E2E tests may need the actual keys. TBD.

Once the local congregations have loaded from the backend, i.e. once state.localCongregations is populated in ./packages/frontend/app/register/components/weekly-meetings-list.tsx, the cards should fade-in from top through to bottom.

Create a nice looking home page

• Create an initial form for entering a location
• Create correct backend call and nice data display
• Display nearby congregations + phone number

This is not urgent as of yet.... as we have no deployments running or something like that. Assign your self

For endpoints like SendCongregationVerificationCode, we need a time-based rate limiter (in middleware) to implement a cooldown period.

Create a dashboard for le admins

Integration tests for our MOST important CRUD actions in our backend.

Some include:

• Congregation
• User

Can write one for tokens after a TBD.

Once the user finds a congregation, route them to a page where we can create their user profile.

Discussion: #7 (comment)

Bug where all 'areas' are holding the value "CONG" for some reason. Lower priority.

For some reason trying to use the nav menu is a pain.... tbh I probably haven't played around with it enough to figure out what's wrong so will keep on trying

This is the error that occurs when trying to use the example provided in the docs

https://ui.shadcn.com/docs/components/navigation-menu

Also not an urgent task as of yet... feel free to assign yourself if you're up to it.

• Create next.js project
• Install shadcn
• Create simple prototype design (can be in figma or just some quick stuff cooked in next, spiced with shadcn :) )

Let's define a project scope as well

The associated phone number with the congregation needs verification. Either by text message or call (there are services that support this). For now, write infrastructure around this for DEV and dummy data. We can look into the actual text messages later.

I'm going to restart making the frontend because I think i made some errors when configuring next/shadcn so instead of trying to manually fix it, I'll save time by redoing it 👍

Create a page where people will easily be able to contact us for support etc.

Just define a simple project architecture. I think it would be a good idea to make use of the wiki page as we can nicely organise and document stuff :)

Investigate how to obtain a phone number for a congregation.

Tasks:

• Research JW.ORG 'weekly-meetings' API
• Add phone number to cong data model

Error on bun dev:

error Unable to parse color from string: hsl(var(--background))
error Unable to parse color from string: hsl(var(--foreground))
error Unable to parse color from string: hsl(var(--primary-foreground))
error Unable to parse color from string: hsl(var(--primary))
error Unable to parse color from string: hsl(var(--secondary-foreground))
error Unable to parse color from string: hsl(var(--secondary))
error Unable to parse color from string: hsl(var(--background))
error Unable to parse color from string: hsl(var(--foreground))
error Unable to parse color from string: hsl(var(--primary-foreground))
error Unable to parse color from string: hsl(var(--primary))
error Unable to parse color from string: hsl(var(--secondary-foreground))
error Unable to parse color from string: hsl(var(--secondary))

This is not a blocker, so can be looked at later.

Fix the home page width issue as introduced by PR #19

Write some tests for the frontend

Create a dashboard for the publishers of the congregation

This probably should have come up in one of my code reviews but that's up to my slacking off a bit probably from reading so much code... but anyways I think this way it will be easier because then won't have to convert the data we get from the geocoding api into strings.

Thoughts on this @JudeDavis1?

Basically create a web version of OnlyM

Write logic to verify new congregations and auth users

Write some unit tests for the backend + frontend

The VERIFIED ADMIN will generate a string of numbers (5 digits) for a user(s) to join the congregation.

• Create the create-token endpoint.
• Write integration tests that cover creation of the token, and verification of the token.

Common app settings may include:

• JW API endpoints
• Loading from .env.secret (environments, DB_URL, etc.)
• User error messages

At the moment, need a CREATE action for a congregation model. When an admin selects a local congregation, it should get sent to the backend, then get created in the database.

Create feature "showroom" pages for the different features we have planned.