Open ekes opened 4 years ago
That makes sense, it's then an editorial decision whether it redisplays to anyone who has already hidden it, rather than a system decision.
Sounds good, I think though we should default to create a new revision in that case, as if theres an update its usually being done in an emergency, and the user story is that when new information is available, the banner is represented.
Tagging as good first issue, may be a little complicated however hopefully something people can get stuck in.
At the moment every time it's save it regenerates the token for the cookie to hide. This could be changed to only change on a new revision?