-
Notifications
You must be signed in to change notification settings - Fork 26
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
BUG- Missing documentation for Polars #1226
Comments
Must be documented on both develop and 4.0.X versions. |
Should you be assigned to this and have this issue in review/Q&A? @toan-quach |
This issue has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this issue, please add another comment or create a PR that links to this issue. If a PR has already been created which refers to this issue, then you should explicitly mention this issue in the relevant PR. Otherwise, you will be unassigned in 14 days. For more information please refer to the contributing guidelines. |
@toan-quach @FlorianJacta Is this issue solved? |
Is there a PR on it? |
@jrobinAV nope not yet, have added to all of the messages raise but not the docstring since this will require changes to the ones in taipy, or a way to inject polars into it. Is it necessary? as I noticed we don't specify all the exposed types in the docstring. |
No. The docstring is not mandatory, but we must update the user manual. Pages data node config and data node usage. |
Bug description
Release notes mentionned that we now support Polars but I have no idea how to use it. I tried putting different strings in exposed type without success.
Either this feature does not exist at all and this is an error inside the doc or if it exists, there are no ways to know how to use it.
This is also what I get when I try to run a code using polars.
Polars is not mentionned.
Test Code:
The text was updated successfully, but these errors were encountered: