Re: [community-group] Status object: simplified audit/decision history (#161)

@jeromefarnum That's a fair comment. I'd still wonder if a few basic status captures might be helpful with more detailed data offset-up as you suggest. IMHO it's only as things mature that this kind of data is useful so storing created, last modified, deprecated, etc may be enough alongside the token to give it context with the option of more details for a full change log for extensions...but this would need to follow a pattern to work cross-platform, which then feels like something that should have a spec

-- 
GitHub Notification of comment by hereinthehive
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/161#issuecomment-1237233603 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 5 September 2022 15:46:57 UTC