Remove duplicate descriptions of fields in Requirement JSON entity
Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: I513da3ba0e1c2c44e078721afeb483976b971ad9
This commit is contained in:
committed by
David Pursehouse
parent
630dcde3a0
commit
89c2b0ddc3
@@ -6812,13 +6812,6 @@ oldest. Empty if there are no related changes.
|
||||
=== Requirement
|
||||
The `Requirement` entity contains information about a requirement relative to a change.
|
||||
|
||||
type:: Alphanumerical (plus hyphens or underscores) string to identify what the requirement is and
|
||||
why it was triggered. Can be seen as a class: requirements sharing the same type were created for a
|
||||
similar reason, and the data structure will follow one set of rules.
|
||||
|
||||
data:: (Optional) Additional key-value data linked to this requirement. This is used in templates to
|
||||
render rich status messages.
|
||||
|
||||
[options="header",cols="1,^1,5"]
|
||||
|===========================
|
||||
|Field Name | |Description
|
||||
|
||||
Reference in New Issue
Block a user