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

link to affected 3rd party test runners in docstring #426

Merged
merged 1 commit into from
Jan 26, 2024

Conversation

seancorfield
Copy link
Contributor

Signed-off-by: Sean Corfield sean@corfield.org

Signed-off-by: Sean Corfield <sean@corfield.org>
@imrekoszo
Copy link
Contributor

@seancorfield thanks for documenting this.

Do you think it would be worth making the contract explicit? If yes, have you got any suggestions on a way to do that?

@seancorfield
Copy link
Contributor Author

Specs for the arguments that cover the required keys and an s/fdef on create itself -- with instrumentation enabled for the tests (I'm assuming there are some tests for create-test-runner).

For now, just a great big reminder in the docstring is probably enough :)

Copy link
Collaborator

@tengstrand tengstrand left a comment

Choose a reason for hiding this comment

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

Looks good!

@tengstrand tengstrand merged commit 9652d1e into polyfy:master Jan 26, 2024
3 checks passed
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