| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 0 | 0 | — |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 0 | — |
What each file covers
Sections
neither file has anyCommands
neither file has anySection tags
neither file has anyLine diff
tyler274/rummage · .cursor/rules/mtgjson_importer.mdc
@@ −1 @@
1---
2description:
3globs: src/cards/mtgjson/**
4alwaysApply: false
5---
6The MTGJSON API importer for cards should include a build macro that actually imports and
7generates card definition rust module files for every card from every set into the src/cards/sets directory.
8
9
10The build macro should update the sets and card definitions if there are are any changes
11or new card/sets. The build macro should also use the cache we implemented to respect API rate limits.
tyler274/rummage · .cursor/rules/cards.mdc
@@ +1 @@
1---
2description:
3globs: src/cards/**
4alwaysApply: false
5---
6please continue refactoring the cards module to be more in line with the docs in docs/
7updating either as needed to improve the robustness of the implementation with unit tests.
8Make sure the docs and the code stay synced. Focus on fixing all the warnings and then the
9failing tests.
10Its ok to remove unused code that has no place in the final implementation, and there should not be much dead code
@@ −1 +1 @@
11 ---
22 description:
3−globs: src/cards/mtgjson/**
3+globs: src/cards/**
44 alwaysApply: false
55 ---
6−The MTGJSON API importer for cards should include a build macro that actually imports and
7−generates card definition rust module files for every card from every set into the src/cards/sets directory.
8−
9−
10−The build macro should update the sets and card definitions if there are are any changes
11−or new card/sets. The build macro should also use the cache we implemented to respect API rate limits.
6+please continue refactoring the cards module to be more in line with the docs in docs/
7+updating either as needed to improve the robustness of the implementation with unit tests.
8+Make sure the docs and the code stay synced. Focus on fixing all the warnings and then the
9+failing tests.
10+Its ok to remove unused code that has no place in the final implementation, and there should not be much dead code
