-
Couldn't load subscription status.
- Fork 168
chore: Use shiny's Makefile to allow for test commands to change over time #1161
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
Conversation
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.
nice, thanks @schloerke !
is there a way to keep the mypy command tested, to check we don't regress the type annotations?
|
Good catch! I lost it in the shuffle yesterday. The I've changed py-shiny's |
|
Working type check: https://github.com/narwhals-dev/narwhals/actions/runs/11293892161/job/31413093004?pr=1161#step:10:48
|
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.
wow amazing, thanks @schloerke !

Related:
What type of PR is this? (check all applicable)
Related issues
Checklist
If you have comments or can explain your changes, please do so below.
The default
pytestcommand does cover some tests, but others are ran under default settings. By integrating the make commands,py-shinycan update the internal script as things change without need for updates tonarwhals.