API v4 #34

Closed
glacials opened this Issue Sep 30, 2016 · 4 comments

Projects

None yet

2 participants

@glacials
Owner

Now that the 2-year transition between the old set release pattern and the new is over, we can remove the ability for the block field in the API to be null. There are a couple of other changes I'd like to make as well, like changing the rough_exit_date format to use quarters rather than "late" or "early/mid". I also might remove the symbol field, as this is not easy to maintain now that our in-page set icons use a font rather than images.

@dgant
dgant commented Sep 30, 2016

I recently started using the whatsinstandard API for ComboDeck (thanks!) to keep its Standard legality in sync with rotations.

When a set is about to rotate into Standard, it seems that most people are interested not in what's currently in Standard, but what's about to be in Standard. For ComboDeck, that'd mean letting people filter cards not just by (What's in Standard) but also (What's in Standard as of the next rotation).

So if the API included information about upcoming Standard sets, that'd be quite handy!

Thank you for running whatsinstandard!

@glacials
Owner

Thanks for the explanation, I can definitely do that!

@glacials glacials added a commit that closed this issue Oct 1, 2016
@glacials API v4. Closes #34. e232071
@glacials glacials closed this in e232071 Oct 1, 2016
@glacials
Owner
glacials commented Oct 1, 2016

There you go!

@dgant
dgant commented Oct 1, 2016

Awesome! I'll work this in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment