Merged
Conversation
This comment was marked as duplicate.
This comment was marked as duplicate.
So, files created by tests aren't checked.
|
I'd suggest moving the formatter test to a separate job. It's unrelated to the specs. And it doesn't need to run in matrix, the behaviour will be identical regardless of which OS it runs on. This might be out of scope of this PR, of course. |
Collaborator
Author
|
I added ameba github action in another PR, so it must do the format check. Now we just need someone to review, approve and merge both PR's |
crimson-knight
approved these changes
Mar 21, 2025
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
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.
Codegen is not tested at all, so before think about fix it is better to add tests for it.
The plan is:
I had some time today and made the tests run against the codegen, still in a "it worked" state, very draft, but I'm pushing it here because if someone with time is interested in fix this there's something to start on.
All codegen tests are tagged with
codegen, currently if you run:crystal spec --tag codegen --fail-fastyou will reproduce issue #87