EC-002: Working on data layer schema updates #6
Conversation
| export const defaultServices = { | ||
| [EServiceNames.SERV_RM]: RMServiceSchema, | ||
| }; | ||
|
|
||
| export const defaultProjects = { | ||
| [EServiceNames.SERV_RM]: { | ||
| name: 'myorg-default-rm-index', | ||
| status: 'active', | ||
| /* | ||
| to-finish: walk the default services | ||
| service: defaultServices.get(‘rickmorty’).name, | ||
| sid: unknown (NEEDS DEFINE RELATIONS) | ||
| */ | ||
| }, | ||
| }; |
There was a problem hiding this comment.
let's finish the walk
src/app/components/system/molecules/divider/client/divider-view.tsx
Outdated
Show resolved
Hide resolved
|
can we default org to community? also, does it makes sense to have different orgs / services / features / abilities adapters/filters (toggling on/off) based on geo location for compliance / regulation? |
|
certain org/local communities; |
|
The Universal Fuzzy Ability algorithm (in lack of a better name), can factor in:
I don't think gender should be relevant, but then if we have a period tracker service/feature, could that be useful? But then, it's PII, and it's easier to just reduce the cardinality. What else matters for regulation? ID verified? ... |
|
e.g. The Vibe Modulator can have different features. |
|
The Fuzzy Ability rules can live in the IAbility interface and we need their corresponding factor in Users and Orgs. |
There was a problem hiding this comment.
LGTM. Since from a data layer perspective this is backwards compatible (unless we enable the schema enforcement, which is not yet tested), I think we should merge this PR and follow up with the missing bit, which is updating the relationship schema definition function in the DB interface singleton.
|
This is to reduce the size of PRs and review/revert overhead. |
PLEASE REVIEW YOUR OWN PR BEFORE OPENING/UN-DRAFTING IT
EC-002
(add link to ticket later)
As the final back end step for this ticket, we need to be able to:
This PR updates the types and schemas to ensure that:
Here is the full flow model:
Here is the model we're aiming to achieve with this PR (skipping some view actions, but using the same model):
Screenshots/Videocasts/Preview Links
Have you?
If so, THANKS! You can pop a beer/soda.
Please open your PR and ping your colleagues to review it on #web-devs channel.
Also, make sure to remind them on a daily basis during stand-up.