Release Notes for version 2.2

This is the list of changes of taipy version 2.2.

Unsupported version

Version 2.2 of Taipy is no longer supported. We strongly recommend that you upgrade to the latest version of Taipy.

Published on 2023-04.

taipy 2.2 contains the latest taipy-config 2.2, taipy-gui 2.2, taipy-core 2.2 and taipy-rest 2.2 packages.

taipy-gui

2.2.0

New features

• A default set of stylesheets are installed with Taipy GUI so that, by default, applications benefit from a homogeneous and good-looking style. This is called the Stylekit.
  The Stylekit can be easily customized to fit your application design's requirements.
• The table and chart controls have a new property called rebuild that can be used if you need to entirely change the data they rely on, including their structure.

Improvements and changes

• The default property name for the part block was changed from render to class_name to allow for directly using the style classes from the Stylekit.
  Please check the section on Styled Sections for more information.
• The expandable block has a new property called on_change enabling to set a specific callback when the block is expanded or collapsed.
• Better error messages when parsing Markdown content.
• Better support for auto-completion in IDE for the Gui.run() configuration parameters, based on a generated Python Interface Definition file.
• The status entry point now provides information about the loaded element libraries and the elements they define.
• The navigate() function and the page property of the part block can now use, as their target, any URL. In the context of a part block, the page will be rendered in an iframe.
  See issue #621.

Deprecations

• Bound variable scope issues fixed when used by elements defined at the root page level.
  See issue #583.
• Filters management fixed in the table controls.
  See issue #667.
• Communication with the server may break.
  See issue #695.

taipy-core

2.2.3

Deprecations

• Error raised when running Orchestrator service in development mode after a function rename in the Config.
  See issue #560.

2.2.2

Deprecations

• PostgreSQL and MySQL engines do not support "driver" argument.
  See issue #544.
  To avoid conflict between engines, the default value of the db_driver parameter in a SQL or a SQL table data node configuration has been removed.