You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if I want to know if a create card has lifelink, or haste for example I need to trawl through the card text attribute, but this is mostly unstructured data.
Using the String.split function with '\n' as the delimiter, some form of which is available in almost or actually every language that has an sdk for the api will produce the exact result you're looking for.
I see the merits of something like this, but I don't know if it's worth development priority given that it can be accomplished with a single line of code on the client-side.
Granted, when I implemented the database for my client-side project, I actually implemented this and it had database normalization benefits, and made implementing certain odd search features (like search by number of distinct effects) quite easy.
Currently if I want to know if a create card has lifelink, or haste for example I need to trawl through the card
text
attribute, but this is mostly unstructured data.eg: https://api.magicthegathering.io/v1/cards?name=banehound
Please include a more structured card attribute for abilities, this will help working with the API.
Bonus points for having an abilities API itself with associated rulings and instructions.
The text was updated successfully, but these errors were encountered: