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

chore: migrate upgrade command to TS and remove legacy implementation #684

Merged
merged 2 commits into from
Sep 9, 2019

Conversation

thymikee
Copy link
Member

@thymikee thymikee commented Sep 9, 2019

Summary:

Part of #683

Had issues with inquirer module typings, they somehow clash with Node. Not sure how to resolve, help wanted :)

Btw decided to remove legacy upgrade implementation, it's about time.

Test Plan:

Green CI

@thymikee thymikee changed the title chore: migrate upgrade command to TS chore: migrate upgrade command to TS and remove legacy implementation Sep 9, 2019
@thymikee thymikee force-pushed the ts/upgrade branch 3 times, most recently from 52ec050 to bc6760d Compare September 9, 2019 20:30
"typescript": "^3.6.2"
},
"devDependencies": {
"@babel/plugin-proposal-class-properties": "^7.5.5"
Copy link
Member

Choose a reason for hiding this comment

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

Why we need it?

Copy link
Member Author

Choose a reason for hiding this comment

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

tests are failing without this transform, not yet sure why

).toMatchSnapshot(
'RnDiffApp is replaced with app name (TestApp and com.testapp)',
);
}, 60000);
test('fetches regular patch, adds remote, applies patch, installs deps, removes remote when updated from nested directory', async () => {
mockFetch(samplePatch, 200);
(execa: any).mockImplementation(mockExecaNested);
((execa as unknown) as jest.Mock).mockImplementation(mockExecaNested);
Copy link
Member

Choose a reason for hiding this comment

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

I usually make it ((execa as any) as jest.Mock), which might be a little bit smaller. It doesn't really matter here :P

Copy link
Member

@Esemesek Esemesek left a comment

Choose a reason for hiding this comment

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

Seems legit. Those // $FlowFixMe are a little bit awkward, but I don't see any other solution to migrating module piece by piece.

@Esemesek Esemesek merged commit 6e68862 into master Sep 9, 2019
@Esemesek Esemesek deleted the ts/upgrade branch September 9, 2019 21:47
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.

2 participants