introduce the "class" key to explicitly define a class of an object

teemtee / tmt

Test Management Tool

MIT License

85 stars 126 forks source link

introduce the "class" key to explicitly define a class of an object #365

Open sopos opened 4 years ago

sopos commented 4 years ago

Currently the object type is determined by presence of some pre-defined keys. There might be a collision by using a key which should identify different object type. This auto-magic is still useful thing but one might want to forcibly override the object type to make i explict. That's where the class key would help. E.g. if I add 'test:' into a plan, the plan is listed in plans and tests as well.

psss commented 4 years ago

To sum up current status, the following are the reserved keys which identify individual metadata levels:

test for tests (L1metadata)
execute for plans (L2 metadata)
story for stories (L3 metadata)

As far as the metadata specification does not allow colliding keys there should not be need for the the new class attribute. But if we need to use the above-mentioned reserved keys across metadata levels in the future, defining a new class attribute could be a solution.