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
I have had a very specific problem: I have an app, which uses interface Card extended by both Debit Card and CreditCard. They are used by DebitAccount and CreditAccount respectively. However when I receive faked CreditCard type for DebitAccount, the app is not built to handle that.
It would be best for me if I could return DebitCard for DebitAccount only, and not to be limited by a random selection from all Card types.
Would there be interest in such functionality? I have already implemented it in my fork, so I can open a PR for it whenever.
The text was updated successfully, but these errors were encountered:
@milansmolik-dragon I added support for __typename in @examples values 72f59ca
and released it as 2.0.0-rc.2 on NPM.
It allows you to do the following:
I have had a very specific problem: I have an app, which uses interface
Card
extended by bothDebit Card
andCreditCard
. They are used byDebitAccount
andCreditAccount
respectively. However when I receive fakedCreditCard
type forDebitAccount
, the app is not built to handle that.It would be best for me if I could return
DebitCard
forDebitAccount
only, and not to be limited by a random selection from allCard
types.Would there be interest in such functionality? I have already implemented it in my fork, so I can open a PR for it whenever.
The text was updated successfully, but these errors were encountered: