Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find a way to represent cards in a maximized, generic sense for backwards compatibility #10

Open
scarletcs opened this issue Jan 8, 2024 · 0 comments
Assignees
Milestone

Comments

@scarletcs
Copy link
Collaborator

ScryfallCards.Any has been received relatively well, with one major setback: many existing systems depend on a more generic system where every card has every possible field present as optional.

We could just do without it, but it'd be helpful to people to provide a card type that has the following properties:

  • All fields that exist on literally every layout will be guaranteed.
  • All fields that MIGHT exist on SOME type will be present but possibly undefined.

The main hangup in this case is Reversible cards which omit several properties usually found present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant