Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only use current fix examples for tests #633 #665

Merged
merged 5 commits into from
Feb 14, 2025
Merged

Conversation

TobiasNx
Copy link
Contributor

@TobiasNx TobiasNx commented Feb 6, 2025

Copy link
Member

@blackwinter blackwinter left a comment

Choose a reason for hiding this comment

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

  • MetafixBindTest.java: I couldn't find anything that needed changing, except for the @MetafixToDos. What do you have in mind?
  • syntax-sample.fix: This one is tricky. It's used specifically to test the Vim plugin, which already has support for some syntax that isn't implemented yet. I don't think we should bother with it too much. As soon as the Metafix grammar is rewritten, I'll see to it that we get boolean operators :)

@blackwinter blackwinter assigned TobiasNx and unassigned blackwinter Feb 7, 2025
@TobiasNx
Copy link
Contributor Author

TobiasNx commented Feb 10, 2025

  • MetafixBindTest.java: I couldn't find anything that needed changing, except for the @MetafixToDos. What do you have in mind?

Yes, the TODOs which are "won't fix"s since the morph collectors and other morph concepts are not reused in Fix anymore. Should we just delete these tests? @blackwinter

* `syntax-sample.fix`: This one is tricky. It's used specifically to test the Vim plugin, which already has support for some syntax that isn't implemented yet. I don't think we should bother with it too much. As soon as the Metafix grammar is rewritten, I'll see to it that we get boolean operators :)

Fine with me

@TobiasNx TobiasNx assigned blackwinter and unassigned TobiasNx Feb 10, 2025
@blackwinter
Copy link
Member

the TODOs which are "won't fix"s since the morph collectors and other morph concepts are not reused in Fix anymore.

Is that so? When was it decided?

Should we just delete these tests?

You should probably ask @fsteeg, since he's the one who introduced them (in f328a13).

If, in fact, we no longer plan to implement those, we should definitely delete the tests IMO.

@blackwinter blackwinter assigned TobiasNx and unassigned blackwinter Feb 10, 2025
@fsteeg
Copy link
Member

fsteeg commented Feb 10, 2025

the TODOs which are "won't fix"s since the morph collectors and other morph concepts are not reused in Fix anymore.

Yes, makes sense, these are probably leftovers from the initial, morph-based approach to implementing fix.

@TobiasNx
Copy link
Contributor Author

Another thing that I spotted is that the java tests still have set_ in them, instead of add_. Should we adjust this here or in #631 ? @blackwinter

@blackwinter
Copy link
Member

I stand by my earlier statement:

all the tests should be left untouched in order to surface any actual behaviour changes once the set_* implementations are changed. Just add new ones where appropriate.

I don't see why it should be addressed here at all. It still is and will be valid syntax.

@TobiasNx TobiasNx merged commit f180907 into master Feb 14, 2025
1 check passed
@TobiasNx TobiasNx deleted the 633-oldSyntax branch February 14, 2025 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants