Oprava vytváření transakce, která nemá typ #19
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@fmasa mergnuto, díky. Ale netuším, jak se to může stát, podle dokumentace to pole je povinné (v dokumentaci "M" jako mandatory):
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moc nechápu, jak taková transakce může na straně Fio vzniknout, ale narazili jsme na situaci, kdy platba, kterou vrátí Fio API má
column8(typ transakce) s hodnotounull. Na takové transakci následně díkystrict_typesumře vytváření objektuTransaction, protože$data->column8->value~>null(+ notice).Přidal jsem pro ten sloupec stejnou kontrolu jako u ostatních nepovinných sloupců, jedinný rozdíl je, že defaultní hodnota je prázdný string místo
null, aby nebylo třeba měnit typ, který vrací getter.