FIX cardDb bug for lazy card loading when issuing a request with a non-existing set code.

Code FIX + Test
Now the implementation in CardDb will automatically try to get the card with that name from an existing edition
This commit is contained in:
leriomaggio
2021-08-28 18:29:07 +01:00
parent a7d1e7398a
commit 8768900cf8
2 changed files with 6 additions and 13 deletions

View File

@@ -94,8 +94,8 @@ public class CardDbTestLazyCardLoading extends ForgeCardMockTestCase {
public void tesLoadAndGetUnsupportedCardHavingWrongSetCode(){
String cardName = "Dominating Licid";
String wrongSetCode = "AA";
String expectedSetCode = CardEdition.UNKNOWN.getCode();
CardRarity expectedCardRarity = CardRarity.Unknown;
String expectedSetCode = "EXO"; // Exodus
CardRarity expectedCardRarity = CardRarity.Rare;
PaperCard dominatingLycidCard = this.cardDb.getCard(cardName);
assertNull(dominatingLycidCard);
@@ -104,11 +104,6 @@ public class CardDbTestLazyCardLoading extends ForgeCardMockTestCase {
FModel.getMagicDb().attemptToLoadCard(cardName, wrongSetCode);
dominatingLycidCard = this.cardDb.getCard(cardName);
assertNull(dominatingLycidCard); // card still not found
// Resorting to Unsupported Card Request
String cardRequest = CardDb.CardRequest.compose(cardName, wrongSetCode);
dominatingLycidCard = this.cardDb.createUnsupportedCard(cardRequest);
assertNotNull(dominatingLycidCard);
assertEquals(dominatingLycidCard.getName(), cardName);
assertEquals(dominatingLycidCard.getEdition(), expectedSetCode);