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

[Feat] Force data types in code #70

Closed
jredwards opened this issue Mar 7, 2023 · 2 comments · Fixed by #96
Closed

[Feat] Force data types in code #70

jredwards opened this issue Mar 7, 2023 · 2 comments · Fixed by #96
Labels
fixed but needs feedback P1 will be fixed in next version

Comments

@jredwards
Copy link

When I'm running pygwalker from a jupyter notebook, any time I reload the cell that runs pygwalker, I have to go back in and adjust data types (quantitative, ordinal, etc). For data where pygwalker makes assumptions that I don't want, that means fussing with the data tab any time I reload the data. Would be great to be able to specify those in the .walk call or elsewhere.

@ObservedObserver ObservedObserver added the P1 will be fixed in next version label Apr 7, 2023
@Asm-Def Asm-Def linked a pull request Apr 9, 2023 that will close this issue
@Asm-Def
Copy link
Collaborator

Asm-Def commented Apr 9, 2023

Hello, thanks for your advice! An argument named fieldSpecs has been provided in #96 and pre-released in pygwalker==0.1.7a3.
Here are some using hints
https://github.com/Kanaries/pygwalker/blob/feat/sup-field-spec-as-args/tests/field-spec.ipynb

@jredwards
Copy link
Author

This is perfect. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed but needs feedback P1 will be fixed in next version
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants