Closed Thorn2910 closed 10 months ago
Seems that sets with issues have this naming in data
whereas stes without this issue have this naming
Hi, thanks for the issue, I have identified the issue and will resolve it quickly !
Actually, it was solved with the latest commit that solve the invalid sorting strategy ! 8fd7afe
It was uploaded to Production and won't happen again !
Thanks for your patience
What seems to be the issue
Set
Field(s)
id or localID
Description
With Javascript SDK
tcgdex.fetch('sets', 'swsh8', 53)
will result in swsh8-153 Pokemon
Same with
tcgdex.fetch('sets', 'swsh8', 2)
will result in swsh8-102 Pokemon
swsh3 seems to have the same issue
Different sets (sv02 / swsh12.5 / swsh12 / swsh9) don't seem to have this issue
Worked yesterday (02.01.24)