Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Link officer pages to participant pages and other way as well #49

Open
5 tasks
harshasrikara opened this issue May 20, 2022 · 0 comments
Open
5 tasks
Labels
enhancement New feature or request

Comments

@harshasrikara
Copy link
Member

Describe new addition
If the same person is listed on both the officer page & the membership page then add a way to navigate between them.

Task List

  • Write script/tool to check both collections for overlapping names. If matches are found then create an object in each officer & participant documents as follows
{
     id: string,
     name: string,
}
  • Update interfaces in the frontend to reflect new field
  • Update UI to include an optional link to navigate to their respective membership/officer page
  • Update documentation with the new schema
  • Update GraphQL API to support this new field (Note: Should be able to query for full officer / participant schema)

Additional context
Although it might seem like a good idea to only include the id from the other collection, this format of storing the name and id in an object ensures consistency across all the collections when storing pointers to other documents. It also simplifies how the GraphQL API can be adapted to perform deep queries since the same technique is used in multiple places.

@harshasrikara harshasrikara added the enhancement New feature or request label May 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant