Skip to content

Meta Models #758

@jon-nfc

Description

@jon-nfc

To reduce the burden and lower the rate of human error. Some models can be made into Meta Models.

Details

For models that can be made into meta models, they should be made so. In this case Model History and Model Notes.

These models are perfect candidates for this as most of the models added to centurion, will have two additional models added due to requiring both history and notes.

A new base model will be required, that will form the basis of the actual data being saved. this base model will be inherited by the meta models.

The following items will be required:

  • A class that generate the relevant Meta model
  • Each model will require an attribute to determine if they need the meta model
  • A single ViewSet to query the relevant Meta models data
  • Permissions to be based off of the Meta model

Tasks

  • Rename current model history tables that will be meta models
  • Rename current model notes tables that will be meta models
  • Update Issue template to remove the requirement for a history model
  • Update Issue template to remove the requirement for a notes model

✅ Requirements

  • Url to be /<parent_model>/<model> i.e. /notes/device
  • Models to have an attribute to determine if they require the meta model
  • Permissions must be based off of the meta model
  • 💯 Must have 100% Unit Test Coverage
  • 💯 Must have 100% Functional Test Coverage

Metadata

Metadata

Assignees

Type

No fields configured for RFE.

Projects

Status

Stale

Relationships

None yet

Development

No branches or pull requests

Issue actions