-
Notifications
You must be signed in to change notification settings - Fork 128
refactor: add canned mock of exports from api-command #642
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,39 @@ | ||
| import { jest } from '@jest/globals' | ||
|
|
||
| import type { Argv } from 'yargs' | ||
|
|
||
| import { | ||
| userAgent, | ||
| type APICommandFlags, | ||
| type apiCommand, | ||
| type apiDocsURL, | ||
| type itemInputHelpText, | ||
| } from '../../lib/command/api-command.js' | ||
| import { buildArgvMockStub, type BuilderFunctionMock } from './builder-mock.js' | ||
|
|
||
|
|
||
| export const apiCommandMocks = <T extends APICommandFlags = APICommandFlags>(prefix: string): { | ||
| apiDocsURLMock: jest.Mock<typeof apiDocsURL> | ||
| itemInputHelpTextMock: jest.Mock<typeof itemInputHelpText> | ||
| apiCommandMock: jest.Mock<typeof apiCommand> | ||
| apiCommandBuilderMock: BuilderFunctionMock<Argv<T>> | ||
| } => { | ||
| const apiDocsURLMock = jest.fn<typeof apiDocsURL>() | ||
| const itemInputHelpTextMock = jest.fn<typeof itemInputHelpText>() | ||
| const apiCommandBuilderMock = buildArgvMockStub<T>() | ||
| const apiCommandMock = jest.fn<typeof apiCommand>() | ||
| jest.unstable_mockModule(`${prefix}/lib/command/api-command.js`, () => ({ | ||
| userAgent, | ||
| apiDocsURL: apiDocsURLMock, | ||
| itemInputHelpText: itemInputHelpTextMock, | ||
| apiCommandBuilder: apiCommandBuilderMock, | ||
| apiCommand: apiCommandMock, | ||
| })) | ||
|
|
||
| return { | ||
| apiDocsURLMock, | ||
| itemInputHelpTextMock, | ||
| apiCommandBuilderMock, | ||
| apiCommandMock, | ||
| } | ||
| } |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't love that we need to pass in the directory prefix here but
jest.unstable_mockModulesworks relative to the test itself. There might be a way to determine this in the module but I haven't found anything yet.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see a better way either. I suppose you could at least set a default (probably of
../../..) so you don't always have to pass it?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had considered that but decided against it because I was afraid someone (like me 😄) might cut-and-paste one without the value specified and wonder why it didn't work.
I've also just realized the small sample of use-cases we have right now might not be representative.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thinking about this for a nanosecond longer and I'm realizing we probably do have more commands at one level deep overall so maybe we should make a default of
../../..? 🤷