Section 31 point 5: the key card shows the model or service
This commit is contained in:
1 parent
ae196f29b7
commit
2dc2622f4b
1 file changed
+9
@@ -127,6 +127,15 @@ function createKeyCard(entry) {
|
||||
top.append(number, status);
|
||||
card.append(top, name, type);
|
||||
|
||||
// The model is documentation only: a hardware key has a model and a cloud key
|
||||
// comes from a service, and an empty value is left out (section 31 point 5).
|
||||
if (entry.model) {
|
||||
const model = document.createElement("p");
|
||||
model.className = "key-model";
|
||||
model.textContent = `${entry.type === "cloud" ? "Service" : "Model"}: ${entry.model}`;
|
||||
card.append(model);
|
||||
}
|
||||
|
||||
// The dates stay visible with an open alert, so the card never hides the last
|
||||
// check and the next due date of a key that only needs an informational
|
||||
// follow-up (section 27).
|
||||
|
||||
Reference in new issue
Block a user