speculative

https://github.com/borkdude/speculative
slipset 2018-10-29T14:23:44.124200Z

I know! I’m very much looking forward to this.

slipset 2018-10-29T14:24:16.124800Z

https://github.com/metosin/spec-tools#data-specs

slipset 2018-10-29T14:24:20.125200Z

might become obsolete 🙂

alexmiller 2018-10-29T14:24:40.125700Z

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

alexmiller 2018-10-29T14:25:02.126Z

will write some more about it when it is available

slipset 2018-10-29T14:25:20.126400Z

Thanks for clarifying, Alex.

slipset 2018-10-29T14:25:48.127Z

If I could chip in on my use case, which may or may not suit the specs:)

slipset 2018-10-29T14:26:40.128400Z

We have some “dynamic” entities, whose shape is defined by the user and stored in our database.

alexmiller 2018-10-29T14:26:57.129100Z

I think the data specs stuff may or may not still be useful, but could at least be retargeted to official apis

slipset 2018-10-29T14:27:19.129500Z

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.

slipset 2018-10-29T14:28:14.130600Z

So I would need to create specs runtime, and then conform against these newly created specs. If that makes sense.

slipset 2018-10-29T14:28:58.131200Z

It’s a bit like a jira issue, right, it can have user defined fields.

alexmiller 2018-10-29T14:29:25.132100Z

I don’t think the story is really different here, it’s just that there will be a no-macro path to doing it

slipset 2018-10-29T14:29:30.132300Z

So, imagine that the atlassian rest api wanted to verify that an issue conformed to spec.