0.3.17

About Pygwalker 0.3.17

• Improved the user experience on Kaggle
• Removed the related code for fid encode, in preparation for providing the calculation field function later
• Added the function of reading cloud datasets (experimental function)

Feat

• feat: raise error when use incorrect view sql #329
• feat: use new preview base graphc-walker canvas #330
• feat: display preview when save and run all in kaggle #331
• feat: add kaggle tips #334
• feat: modify display_chart from png to canvas #335
• feat: add cloud dataset create and explore #337
• feat: delete share cloud charts feature #338
• feat: remove encoding field name #339
• feat: file type of the uploaded file dataset from csv to parquet #340

Fix

• fix: add export config field and kaggle preview style #332
• fix: add workflow field when invoke upload_spec_to_cloud #336
• fix: fix bugs of removing fid encode #343

@longxiaofei

Full Changelog: 0.3.16...0.3.17

0.3.16

About Pygwalker 0.3.16

• exporting the current chart data into a dataframe of pandas in jupyter notebook, refer: How to export your current chart data to a dataframe?
• fix temproal timezone bugs and other bugs.

What's Changed

• feat: add export dataframe tool by @longxiaofei in #321
• fix: temproal timezone bugs by @longxiaofei in #325
• fix: read ksf config failed when not set token and remove log print by @longxiaofei in #327

Full Changelog: 0.3.15...0.3.16

0.3.16a0

About Pygwalker 0.3.16a0

Users can export the current chart data into a dataframe of pandas in jupyter notebook. This feature also prepares for the export various calculation measures provided by graphch-walker in the future, detail refer: How to export your current chart data to a dataframe?

What's Changed

• feat: add export dataframe tool by @longxiaofei in #321

Full Changelog: 0.3.15...0.3.16a0

0.3.15

What's Changed

• fix: pure renderer params bugs in streamlit by @longxiaofei in #320

Full Changelog: 0.3.14...0.3.15

0.3.14

About Pygwalker 0.3.14

• modify request way of ask-viz api.
• update graphic-walker, to fix some bugs of dsl to sql.

What's Changed

• feat: modify request way of ask-viz api by @longxiaofei in #318

Full Changelog: 0.3.13...0.3.14

0.3.13

About Pygwalker 0.3.13

• Mainly to fix a lot of bugs, include dsl-to-sql, import new graphic-walker.
• Updated graphic-walker version

What's Changed

• fix: modify IGlobalStore to VizSpecStore #315
• fix: filter bugs in connector and duckdb && add chart exists tips when create shared chart #316

Full Changelog: 0.3.12...0.3.13

0.3.12

What's Changed

• feat: update graphic-walker to 0.4.25 by @longxiaofei in #308
• feat: hide cloud tips when privacy is offline by @longxiaofei in #309
• fix: fix timestamp field to sql bugs by @longxiaofei in #312

Full Changelog: 0.3.11...0.3.12

0.3.12a0

What's Changed

• feat: update graphic-walker to 0.4.25 #308

@longxiaofei

Full Changelog: 0.3.11...0.3.12a0

0.3.11

Fix

• fix: streamlit api - get_streamlit_html #306

Full Changelog: 0.3.10...0.3.11

0.3.10

About PyGWalker 0.3.10

Cloud Config (Specification)

In this update, we provide enhanced spec with cloud to allow you to save and share your charts through cloud. Here is an example you can use could file to save your spec:

walker = pyg.walk(df, spec="ksf://<workspace_name>/<file_path>")

Check this document for detail usage: Use cloud config in pygwalker to save your spec

New Configuration And Privacy Policy

We update privacy policy and refactor code of setting config， more details: How to set your privacy configuration?

[pygwalker privacy policy]
offline: fully offline, no data is send or api is requested
update-only: only check whether this is a new version of pygwalker to update
events: share which events about which feature is used in pygwalker, it only contains events data about which feature you arrive for product optimization. No DATA YOU ANALYSIS IS SEND.

Add Track Collector

We will collect some metrics to optimize pygwalker users' and developers' experience (whether you arrive at a feature), which will not involve user data.
If you do not want to share this, you can set your privacy policy to "update-only" or "offline".

Host and Share PyGWalker in Cloud(Experimental Features)

We are testing a feature that allows you to publish your charts with online code or just one click. Then, you can use the published charts as a web app to share with others or as an embeddable live component to integrate with other systems.

from pygwalker.api.kanaries_cloud import create_cloud_walker, walk_on_cloud

# create a cloud pygwalker
create_cloud_walker(df, chart_name="pyg-test", workspace_name="xxxxx")

# render ui of cloud pygwalker
walk_on_cloud("xxxxx", "pyg-test")

How to cancel showing cloud tools

pygwalker 0.3.10 displays buttons related to cloud tools by default, If you don't want to display it, please run code:

import pygwalker as pyg

pyg.walk(df, show_cloud_tool=False)

Feat

• feat: add vizgpt feature(temporary) #279
• feat: add cloud config file read and write #280
• feat: store local user id #286
• feat: modify cloud server tips #287
• feat: add communication on gradio(pre-demo) #289
• feat: avoid read config files from affecting the main feature #290
• feat: add new feature walk_on_cloud #296
• feat: add track collector by #299
• feat: avoid kanaries_token being rendered directly on the html by #300
• feat: cancel log of update version #301
• feat: add upload cloud spec tips when spec params is none #303

Refactor

• refactor: pygwalker config utils #285
• refactor: streamlit module #297
• refacotr: split fucntion from create_cloud_graphic_walker #298

Fix

• fix: communications can't work when gradio reload #291

@longxiaofei

Full Changelog: 0.3.9...0.3.10