Greenstand / Greenstand/treetracker-messaging-api

Naming of tables, fields and design unclear

Open
#84 0 comments 0 reactions 0 assignees View on GitHub
documentation question
Dominant language
JavaScript
Stars
1
Forks
11
PR merge metrics
No merged PRs in 30d

Description

It is time to get the messaging functionality into production as an added module looking at the future keycloak implementation.

Some questions and clarifications when looking at the attached ER.

1. It seems that "author.id" is used in "message.sender_id" as the reference. Why is there another reference since it is referenced through the content.author_id

2. Why is "bulk_message.author_handle" written out as handle(varchar) and not referenced as an id?

3. I am assuming that author will be populated or synced with treetracker.grower_account? This should be activated for all users right?

4. How does the stakeholder.stakeholder fit in here? Assumption: keycloak will manage admin panel users and stakeholder accounts which then allow admin panel users to send messages under the stakeholders names and details.

5. Is the messaging ER still up to date for the post domain migration v2 data structure?

![Screenshot 2023-05-26 at 07 46 49](https://github.com/Greenstand/treetracker-messaging-api/assets/3283800/9897f59f-0440-4021-b1d3-d653e4a1b03f)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.