full name field for cards with 2+ faces #13
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
Keep the full name field of the main card entry when requesting a card with two or more card_faces, including the double slashes as separator
terralullabyte
approved these changes
Feb 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Keep the full name field of the main card entry when requesting a card with two or more card_faces, including the double slashes as separator
currently, when requesting a card like "Wear // Tear", the function only returns "Wear" in the name field. This fix addresses that and copies the full name "Wear // Tear" into the name field of the first card_face.
Alternatively, a new field "full_name" (for example) could be defined, to maintain backward compatibility.