https://twitter.com/stuarthalloway/status/1056881838927568896
I know! I’m very much looking forward to this.
might become obsolete 🙂
I have it pushed on the stack at the moment behind some more error reporting work, but it’s in progress. it’s not going to be like schema so I wouldn’t expect that
will write some more about it when it is available
Thanks for clarifying, Alex.
If I could chip in on my use case, which may or may not suit the specs:)
We have some “dynamic” entities, whose shape is defined by the user and stored in our database.
I think the data specs stuff may or may not still be useful, but could at least be retargeted to official apis
So a thing has some fields that are statically known to us, and some fields which we would have to look into the database to figure out the shape of.
So I would need to create specs runtime, and then conform against these newly created specs. If that makes sense.
It’s a bit like a jira issue, right, it can have user defined fields.
I don’t think the story is really different here, it’s just that there will be a no-macro path to doing it
So, imagine that the atlassian rest api wanted to verify that an issue conformed to spec.