Add failsafe error catch if card object is undefined during metadata initialisation #477
No reviewers
Labels
No labels
blocked
duplicate
needs criteria
needs estimate
needs tests
question
requires documentation
type
admin
type
alert
type
bug
type
change
type
defect
type
dependencies
type
epic
type
investigation
type
spike
type
story
type
subtask
won't fix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
External/card-drop!477
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/473-card-object-undefined"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
#473
I'll review this diff for you. This appears to be a bug fix with added test coverage for the
CardMetadataFunction.Summary
The changes fix a bug where only the first series in a JSON file was validated for cards, and adds comprehensive unit tests to prevent regression.
Verdict
Approve with minor fixes - The core bug fix is solid and the tests are valuable. Just fix the typo in the function name and consider the validation ordering question.
@ -0,0 +1,43 @@import {CardMetadata} from "../../../src/contracts/SeriesMetadata";// eslint-disable-next-line @typescript-eslint/no-explicit-any -- Required to test non-confirmed json dataexport default function GenenerateSeriesMetadata(id: number, name: string, generateSeries: number = 1, generateCards: number | number[] = 1): any[] {Typo in Function Name
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.