mirror of
https://github.com/datahub-project/datahub.git
synced 2025-08-22 08:08:01 +00:00
843a6c5bbb
* Releases updated version of datahub-web client UI code * Fix typo in yarn lock * Change yarn lock to match yarn registry directories * Previous commit missed some paths * Even more changes to yarnlock missing in previous commit * Include codegen file for typings * Add files to get parity for datahub-web and current OS datahub-midtier * Add in typo fix from previous commit - change to proper license * Implement proper OS fix for person entity picture url * Workarounds for open source DH issues * Fixes institutional memory api and removes unopensourced tabs for datasets * Fixes search dataset deprecation and user search issue as a result of changes * Remove internal only options in the avatar menu
26 lines
929 B
Markdown
26 lines
929 B
Markdown
@datahub/entities
|
|
==============================================================================
|
|
|
|
This package holds entity specific components and modules.
|
|
|
|
## Creating an entity module
|
|
|
|
Modules for entities should be namespaced according to the entity in the format:
|
|
|
|
```
|
|
<module-type>/<pluralized-entity-name>/<entity-module-path>
|
|
```
|
|
|
|
where `module-type` is the name of the module we are working with (for example, `component`
|
|
or `util`), `pluralized-entity-name` is the identifier for the entity in plural form (for example,
|
|
`datasets` or `metrics`) and `entity-module-path` is the specific organization we want for the
|
|
module.
|
|
|
|
With the above criteria, when we create an upstream datasets component for datasets with respect to
|
|
relationships, the command we might run might be:
|
|
|
|
```
|
|
// Creates the module components/datasets/relationships/upstream-datasets.ts
|
|
ember g component datasets/relationships/upstream-datasets
|
|
```
|