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
[KED-2615] Nudge user to upgrade Kedro-Viz from the CLI #690
Conversation
| cd package && isort . | ||
| black package/kedro_viz package/tests package/features | ||
| pylint --rcfile=package/.pylintrc -j 0 package/kedro_viz | ||
| pylint --rcfile=package/.pylintrc -j 0 --disable=protected-access,missing-docstring,redefined-outer-name,no-self-use,invalid-name,too-few-public-methods,no-member,unused-argument,duplicate-code package/tests | ||
| pylint --rcfile=package/.pylintrc -j 0 --disable=missing-docstring,no-name-in-module,unused-argument package/features | ||
| flake8 --config=package/.flake8 package | ||
| mypy --config-file=package/mypy.ini package |
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 changed this in another PR to parallelise this step but I didn't know & and wait doesn't work on makefile across serveral lines, so I reverted it here.
|
Do we want to make a note about Kedro-Viz being designed to be backward compatible? |
Nice change, and
Just a couple of ideas - nothing big, so feel free to ignore:
- should we explain why a user might want to upgrade? "It's backwards-compatible so will work with your current project straight away and will let you use lots of cool new features"
- is there any way of making it even easier for someone to run the
pip install -Ucommand so they don't even need to copy/paste it? Like somehow making it clickable or so they just type "y" to execute it (this would be annoying though because you get all the kedro viz console messages after that). I think probably not, but just mentioning it in case you are struck with inspiration
|
@AntonyMilneQB @datajoely yea happy to highlight it if someone can help me with the wording. It's already quite long. @AntonyMilneQB re autoupdate: yes, that's the next iteration. This is a quick fix first, then the idea is we do autoupdate like VSCode or even from the CLI. But that's more involved (need to launch and manage another process, etc.) |
Signed-off-by: Lim Hoang <limdauto@gmail.com>
Signed-off-by: Lim Hoang <limdauto@gmail.com>


Description
This PR shows a warning to encourage user to upgrade Kedro-Viz if there is a newer version on PyPI.
Development notes
QA notes
I have tested this manually
Checklist
RELEASE.mdfileThe text was updated successfully, but these errors were encountered: