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

WIP: ts-migration/valid-expect #333

Closed
wants to merge 1 commit into from
Closed

WIP: ts-migration/valid-expect #333

wants to merge 1 commit into from

Conversation

yatki
Copy link
Contributor

@yatki yatki commented Jul 22, 2019

No description provided.

@yatki
Copy link
Contributor Author

yatki commented Jul 22, 2019

@G-Rath I saw you did quite a lot work on migrating rules. Please take a look to this PR to avoid duplicating anything. I hope this helps :) Feel free to give feedback if you have better solutions.

Cheers,

@SimenB
Copy link
Member

SimenB commented Jul 22, 2019

Woo! 🎉

I'll be merging the TS migration shortly btw, including some heavy rebase work (I can do it for you if you want). So you can change this PR to point to master.

EDIT: I've rebased and changed this to point to master 🙂

@SimenB SimenB mentioned this pull request Jul 22, 2019
35 tasks
@SimenB SimenB changed the base branch from reapply-ts to master July 22, 2019 00:39
@yatki
Copy link
Contributor Author

yatki commented Jul 22, 2019

@SimenB Thank you very much. I'll continue to work on it as soon as I have time this week (shouldn't be longer than 2-3 days).

@G-Rath
Copy link
Collaborator

G-Rath commented Jul 22, 2019

This is awesome thanks!

I have already started a bit on this rule, but was also putting it off to do last as it uses most of the matchers. Instead I was aiming to convert some of the other guards first via rules that use less of them.

You've got a good base there that'll only get better - I can already see a few changes that will be required, and you shouldn't use any casts by the end of the conversation.

I'm currently in Melbourne until Wednesday for work, so I'll be working on the conversation on and off until the weekend, where I hope to go full force to get it finished by Monday :)

tbh, part of me is wanting to put a hold on the conversation for a few days, just to see if #317 has caused any problems (which I think it might have w/ #334 😬)

Let me know if you'd like me to do any work on this branch at all, or have any questions :)

@SimenB
Copy link
Member

SimenB commented Aug 12, 2019

🎉 This issue has been resolved in version 22.15.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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.

None yet

3 participants