-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Updated utils.py for better warning messages #617
Updated utils.py for better warning messages #617
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.
check also the linter comments
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.
👌
how do i resolve these linter errors |
Hello @srinivaspavan9, sorry for the late response. First you need to merge your branch with the latest Avaiga:develop branch. Then, in the linter error log, I saw that
which means that the line you edited is too long. Please address the issue before we can merge your change to Taipy. Thank you |
Hi @srinivaspavan9, |
504caaf
into
Avaiga:feature/#379-better-message
* Updated utils.py for better warning messages (#617) * Updated utils.py for better warning messages * added value check for dataframe * added the check at the warning level * resolved linter comments * added required changes * Linter Changes * Linter Changes --------- Co-authored-by: Fred Lefévère-Laoide <[email protected]> * format and small fix * Update taipy/gui/_renderers/utils.py Co-authored-by: Fabien Lelaquais <[email protected]> * Update taipy/gui/_renderers/utils.py Co-authored-by: Fabien Lelaquais <[email protected]> * mypy * linter --------- Co-authored-by: Srinivas Pavan <[email protected]> Co-authored-by: Fred Lefévère-Laoide <[email protected]> Co-authored-by: Fabien Lelaquais <[email protected]>
Updated Warning Message in utils.py for Issue #379
This PR addresses BUG-Inputting the wrong column name in a chart reports empty data (#379). The issue was due to the misleading warning message in
utils.py
, which implied an empty DataFrame when a non-existent column name was used.Changes Made:
Screenshot after the change: