Carbon coverage: Start Acceptance criteria for hidden items

[RichKummer]

The ability to hide unhelpful or inaccurate issue items is an important feature to the Carbon coverage plugin. This enables designers to flag certain items so they do not take. up space in the plugin UI and can safely be ignored. However, memory can become an issue with too many recorded hidden items.

We need to start figuring out the acceptance criteria for when the plugin should delete a hidden item.

For example:

1. The memory of all hidden items should be cleared whenever the designer closes the Figma file running the plugin.

Every time you store you need a key and a value. Right now, everything is stored under one key. We can have multiple keys scoped to certain things like documents. We can then limit it to search through certain keys (like only document ID).

See below.

[RichKummer]

Hidden items should be cleared when...

• TBD

Hidden items should be retained when...

• TBD

Or we can map by priority:

Priority 01

• TBD

Priority 02

• TBD

Priority 03

• TBD