Skip to content

Conversation

@muz
Copy link
Contributor

@muz muz commented Jan 25, 2026

I'm eager to actually have this test run and deliver value given various other bits of tinkering I've done, and plan to do around tokens.

I think there's some value to this test as is, especially around stating what desired state is even if the codebase isn't there today.

So;

  • Unmark the test as @Ignored
  • Comment out selectively the parts which actively throw errors today, due to implementation details
  • Allow this to run to catch either the introduction of new errors, or regressions

Running this locally, it passes on the tip of master, albeit it does produce a number of info and warning messages that are visible in the surefire reports. I think this is fine, and do not think it's worth addressing them all quite yet as some of these are tied up in the more fundamental and far reaching aim to move things that should be using CreatureToken to doing that.

…hecks to establish a baseline for regressions
@github-actions github-actions bot added the tests label Jan 25, 2026
// // how-to fix:
// // - public token must be downloadable, so tok-data must contain miss set
// // (also don't forget to add new set to scryfall download)
// errorsList.add("Error: can't find data in tokens-database.txt for token: " + tokenClass.getName() + " -> " + token.getName());
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thats wrong fix style.

If you need to disable critical checks then must temporary move it to warningsList and add todo about fix and return to errorsList after project fix.

Commented code is bad thing and can be removed as dirty/outdated code by someone later, but it’s not outdated here, it’s just require a project fixes before enable.

Another approach is feature flag (boolean const) to enable/disable that check

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I don't think this code is outdated, but we definitely don't want it blocking right now either.

I am willing to take the time to fix the underlying things that block enabling these checks too, but in the mean time think the other parts of this check are worth having. 💪

Happy to refactor this as advised, either through demoting to warnings for now, or hiding behind flags, until I get around to fixing them, having the code stable, and the checks pass when executed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved behind a flag with a note that the first thing anyone (probably me 😁) should do is address private tokens being declared instead of CreatureToken being used.

When correcting to using CreatureToken, fixes can be made for offending naming styles etc too which will greatly reduce the number of classes to address that are flagged for multiple check violations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants