Merge branch 'main' into clarasb-101_select_component_add_multiple

Author: clarasb

README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/bcdev/chartlets/actions/workflows/frontend-ci.yml/badge.svg)](https://github.com/bcdev/chartlets/actions/workflows/frontend-ci.yml)
 [![codecov](https://codecov.io/gh/bcdev/chartlets/graph/badge.svg?token=zJBPMFvnpg&flag=frontend)](https://codecov.io/gh/bcdev/chartlets)
-[![npm](https://badge.fury.io/js/chartlets.svg)](https://npmjs.org/package/chartlets)
+[![NPM Version](https://img.shields.io/npm/v/chartlets)](https://www.npmjs.com/package/chartlets)
 
 [![CI](https://github.com/bcdev/chartlets/actions/workflows/backend-ci.yml/badge.svg)](https://github.com/bcdev/chartlets/actions/workflows/backend-ci.yml)
 [![codecov](https://codecov.io/gh/bcdev/chartlets/graph/badge.svg?token=zJBPMFvnpg&flag=backend)](https://codecov.io/gh/bcdev/chartlets)

chartlets.js/CHANGES.md

@@ -1,145 +1,154 @@
 ## Version 0.1.4 (in development)
 
-* Add `multiple` property for `Select` component to enable the
+- Add `multiple` property for `Select` component to enable the
   of multiple elements.
 
-## Version 0.1.0 (in development)
+## Version 0.1.3 (from 2025/01/28)
 
-* Reorganised Chartlets project to better separate demo from library code.
+- **Chore:** Version bump to align CI process with GitHub release flow.
+  No functional changes. This release ensures proper triggering of the CI
+  pipeline for publishing and NPM.
+
+## Version 0.1.0 (from 2025/01/14)
+
+- Reorganised Chartlets project to better separate demo from library code.
   Using monorepo layout for `chartlets.js` with workspaces `lib` and `demo`
   that host the packages for `chartlets` and `chartlets-demo`.
 
-* Other code reorganisations:
-  - moved `component/Registry` into `store` 
-  - renamed module `component` into `components` 
+- Other code reorganisations:
+
+  - moved `component/Registry` into `store`
+  - renamed module `component` into `components`
   - no longer exposing `Registry` type
 
-* Chartlets now allows for plugins that can provide individual component 
+- Chartlets now allows for plugins that can provide individual component
   implementations.
-  The Vega-based chart and MUI components are now optional and have been 
+  The Vega-based chart and MUI components are now optional and have been
   moved into respective plugin modules `chartlets/plugins/vega` and
   `chartlets/plugins/mui`.
-  To activate them, use the new `plugins: PluginLike[]` option 
+  To activate them, use the new `plugins: PluginLike[]` option
   of `FrameworkOptions`:
+
   ```TypeScript
   import { configureFramework } from "chartlets";
   import mui from "chartlets/plugins/mui";
   import vega from "chartlets/plugins/vega";
-  
-  configureFramework({ plugins: [mui(), vega()], ... });   
+
+  configureFramework({ plugins: [mui(), vega()], ... });
   ```
 
-* Renamed `Plot` component into `VegaChart`.
+- Renamed `Plot` component into `VegaChart`.
 
-* The new `VegaChart` component respects a `theme` property. If not given,
+- The new `VegaChart` component respects a `theme` property. If not given,
   it will respect the current theme mode `"dark"` otherwise fallback to the
-  Vega default theme. 
+  Vega default theme.
 
-* The demo application now allows for switching the theme mode between
+- The demo application now allows for switching the theme mode between
   dark, light, and system mode.
 
-* Changed the yet unused descriptor type `CbFunction` for callback functions.
+- Changed the yet unused descriptor type `CbFunction` for callback functions.
+
   - using `schema` instead of `type` property for callback arguments
   - using `return` object with `schema` property for callback return values
 
-* New (MUI) components
+- New (MUI) components
+
   - `Divider`
   - `LinearProgress`
   - `RadioGroup` and `Radio`
   - `Switch`
   - `Tabs`
   - `Slider`
 
-* Supporting `tooltip` property for interactive MUI components.
+- Supporting `tooltip` property for interactive MUI components.
 
 ## Version 0.0.29 (from 2024/11/26)
 
-* Resolved warnings that appeared when using Vega charts.
+- Resolved warnings that appeared when using Vega charts.
 
 ## Version 0.0.28 (from 2024/11/26)
 
-* Updated docs.
+- Updated docs.
 
 ## Version 0.0.27 (from 2024/11/25)
 
-* Added component `IconButton` and enhanced other components' attributes.
+- Added component `IconButton` and enhanced other components' attributes.
 
 ## Version 0.0.26 (from 2024/11/23)
 
-* Channels such as `Input`, `State`, `Output` no longer have a `link` property.
+- Channels such as `Input`, `State`, `Output` no longer have a `link` property.
   Instead, we use a special `id` format, namely `"@app"` and `@container`
   to address states other than components. (#52)
 
 ## Version 0.0.25 (from 2024/11/23)
 
-* `Registry.register()` now requires the `type`
+- `Registry.register()` now requires the `type`
   to be passed as 1st argument because `component.name` will
   be a mangled name in most cases.
 
 ## Version 0.0.24 (from 2024/11/23)
 
-* Exporting required `HostStore` type.
+- Exporting required `HostStore` type.
 
 ## Version 0.0.23 (from 2024/11/23)
 
-* Introduced new interface `HostState` that applications may implement
+- Introduced new interface `HostState` that applications may implement
   to provide computed properties, i.e., a derived state. (#43)
 
-* Replacing entire components if a related component `StateChange` 
+- Replacing entire components if a related component `StateChange`
   has an empty `property`. (#38)
 
-* Added handy hooks `useContributions` and `useComponentChangeHandlers`.
-
+- Added handy hooks `useContributions` and `useComponentChangeHandlers`.
 
 ## Version 0.0.22 (from 2024/11/19)
 
-* Improved robustness while rendering the in `Select` component
+- Improved robustness while rendering the in `Select` component
   wrt `options` property.
 
-* `Button` component now sets a `clicked: boolean` property instead
+- `Button` component now sets a `clicked: boolean` property instead
   of `n_clicks: int`.
 
 ## Version 0.0.21 (from 2024/11/19)
 
-* `Component` children can now also be text nodes (of type `string`).
+- `Component` children can now also be text nodes (of type `string`).
 
-* `Typography` component has children instead of `text`.
+- `Typography` component has children instead of `text`.
 
-* A component's `children` property can now be changed, even from a
+- A component's `children` property can now be changed, even from a
   scalar.
 
-* Renamed `Dropdown` component into `Select`
+- Renamed `Dropdown` component into `Select`
   (to refer to MUI component with same name).
 
-* `Select` component has more flexible options.
+- `Select` component has more flexible options.
 
 ## Version 0.0.20 (from 2024/11/19)
 
-* Using `FrameworkOptions.getDerivedHostState` also in
+- Using `FrameworkOptions.getDerivedHostState` also in
   `handleHostStoreChange()`.
 
-* Actions `handleComponentChange()` and `handleHostStoreChange()`
+- Actions `handleComponentChange()` and `handleHostStoreChange()`
   now exit immediately, if no extensions are configured yet.
 
-* Module `utils.objPath`: Renamed `toObjPath` into `normalizeObjPath`, 
+- Module `utils.objPath`: Renamed `toObjPath` into `normalizeObjPath`,
   added `formatObjPath`.
 
 ## Version 0.0.19 (from 2024/11/18)
 
-* Fixed TypeScript typing issues with `configureFramework<S>()` and
+- Fixed TypeScript typing issues with `configureFramework<S>()` and
   `FrameworkOptions`.
-  
+
 ## Version 0.0.18 (from 2024/11/18)
 
-* Fixed TypeScript typing issues with `configureFramework<S>()` and 
-  `FrameworkOptions`. 
+- Fixed TypeScript typing issues with `configureFramework<S>()` and
+  `FrameworkOptions`.
 
 ## Version 0.0.17 (from 2024/11/18)
 
-* Enhanced interface `FrameworkOptions` by property `getDerivedHostState`,
+- Enhanced interface `FrameworkOptions` by property `getDerivedHostState`,
   which is a user-supplied function that can compute derived
-  host state property. 
-  
+  host state property.
+
 ## Version 0.0.16 (from 2024/11/12)
 
-Initial, still experimental version. 
+Initial, still experimental version.

chartlets.js/README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/bcdev/chartlets/actions/workflows/frontend-ci.yml/badge.svg)](https://github.com/bcdev/chartlets/actions/workflows/frontend-ci.yml)
 [![codecov](https://codecov.io/gh/bcdev/chartlets/graph/badge.svg?token=zJBPMFvnpg&flag=frontend)](https://codecov.io/gh/bcdev/chartlets)
-[![npm](https://badge.fury.io/js/chartlets.svg)](https://npmjs.org/package/chartlets)
+[![NPM Version](https://img.shields.io/npm/v/chartlets)](https://www.npmjs.com/package/chartlets)
 ![](https://img.shields.io/badge/Linting-TypeScript%20%26%20Prettier-blue?logo=typescript&logoColor=white)
 
 Chartlets is a software framework that allows websites developed with

chartlets.js/package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "chartlets-demo",
-  "version": "0.1.0",
+  "version": "0.1.3",
   "description": "Demonstrator for the Chartlets framework.",
   "type": "module",
   "files": [

chartlets.js/packages/demo/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chartlets",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "An experimental library for integrating interactive charts into existing JavaScript applications.",
   "type": "module",
   "files": [

chartlets.js/packages/lib/package.json

@@ -1,75 +1,80 @@
 ## Version 0.1.4 (in development)
 
-* Add `multiple` property for `Select` component to enable the
+- Add `multiple` property for `Select` component to enable the
   of multiple elements.
-  
+
+## Version 0.1.3 (from 2025/01/28)
+
+- **Chore:** Version bump to align CI process with GitHub release flow.
+  No functional changes. This release ensures proper triggering of the CI
+  pipeline for publishing to PyPI.
+
 ## Version 0.1.0 (from 2025/01/14)
 
-* Reorganised Chartlets project to better separate demo from library code. 
-  Created separate folder `demo` in `chartlets.py` that contains 
+- Reorganised Chartlets project to better separate demo from library code.
+  Created separate folder `demo` in `chartlets.py` that contains
   a demo `server` package and example configuration.
   Also simplified demo server code:
+
   - Moved `panel` module one level up
-  - Removed `util` module which was no longer required 
+  - Removed `util` module which was no longer required
 
-* Allow for different chart providers. `VegaChart` can be configured only if 
+- Allow for different chart providers. `VegaChart` can be configured only if
   `altair` package is installed.
-  
-* Renamed `Plot` into `VegaChart`, which now also respects a `theme` property. 
+- Renamed `Plot` into `VegaChart`, which now also respects a `theme` property.
+
+- Changed schema of the yet unused descriptor for callback functions.
 
-* Changed schema of the yet unused descriptor for callback functions.
   - using `schema` instead of `type` property for callback arguments
   - using `return` object with `schema` property for callback return values
 
-* Added `tooltip` property to interactive components.
+- Added `tooltip` property to interactive components.
 
-* New components
+- New components
   - `Divider`
   - `RadioGroup` and `Radio`
   - `Switch`
   - `Slider`
   - `Tabs` and `Tab`
- 
 
 ## Version 0.0.29 (from 2024/11/26)
 
-* Fixed a bug that prevents using annotations of type `dict` or `dict[str, T]`.
+- Fixed a bug that prevents using annotations of type `dict` or `dict[str, T]`.
   in callback functions.
-* Introduced a callback function in `my_panel.py` to handle click events. 
+- Introduced a callback function in `my_panel.py` to handle click events.
   Demonstrates how to dynamically change the color of a clicked bar.
 
-
 ## Version 0.0.28 (from 2024/11/26)
 
-* Updated docs.
+- Updated docs.
 
-* Added component `IconButton` and enhanced other components' attributes.
+- Added component `IconButton` and enhanced other components' attributes.
 
-* Channels such as `Input`, `State`, `Output` no longer have a `link` property. 
-  Instead, we use a special `id` format, namely `"@app"` and `@container` 
-  to address states other than components. 
-  This way, the call syntax `Input(id, property)` is the same for all states, 
-  e.g., `Input("@app", "selectedDatasetId")`, instead of 
+- Channels such as `Input`, `State`, `Output` no longer have a `link` property.
+  Instead, we use a special `id` format, namely `"@app"` and `@container`
+  to address states other than components.
+  This way, the call syntax `Input(id, property)` is the same for all states,
+  e.g., `Input("@app", "selectedDatasetId")`, instead of
   `Input(source="app", property="selectedDatasetId")`. (#52)
 
-* Added progress components `CircularProgress`, `CircularProgressWithLabel`, 
+- Added progress components `CircularProgress`, `CircularProgressWithLabel`,
   `LinearProgress`, `LinearProgressWithLabel`.
 
-* Replacing components is now possible by using an 
+- Replacing components is now possible by using an
   `Output` with `property` set to an empty string. (#38)
 
-* `Component` children can now also be text nodes (of type `string`).
+- `Component` children can now also be text nodes (of type `string`).
 
-* `Typography` component has children instead of `text`.
+- `Typography` component has children instead of `text`.
 
-* Renamed `Dropdown` component into `Select`
+- Renamed `Dropdown` component into `Select`
   (to refer to MUI component with same name).
 
-* `Select` component has more flexible options.
+- `Select` component has more flexible options.
 
-* Dealing with callbacks parameter and return types 
+- Dealing with callbacks parameter and return types
   that are just `list` and not, e.g., `list[str]`.
- 
+
 ## Version 0.0.16 (from 2024/11/12)
 
-Initial, still experimental version. 
+Initial, still experimental version.

chartlets.py/CHANGES.md

@@ -1 +1 @@
-version = "0.1.0"
+version = "0.1.3"