Release v0.7.4 (#242)

* Fixed dataset/widget name uniqueness requirement that was preventing
dashboards being deployed
([#241](#241)). A fix has
been implemented to address a uniqueness requirement issue with the
dataset/widget name that was preventing dashboard deployment. A new
`widget` instance is now created with a unique name, generated by
appending `_widget` to the metadata ID, in the `get_layouts` method.
This ensures that multiple widgets with the same ID but different
content can exist in a single dashboard, thereby meeting the name
uniqueness requirement. In the `save_to_folder` method, the widget name
is modified by removing the `_widget` suffix before writing the textbox
specification to a markdown file, maintaining consistency between the
widget ID and file name. These changes are localized to the
`get_layouts` and `save_to_folder` methods, and no new methods have been
added. The existing functionality related to the creation, validation,
and saving of dashboard layouts remains unaltered.

CHANGELOG.md

@@ -1,5 +1,10 @@
 # Version changelog
 
+## 0.7.4
+
+* Fixed dataset/widget name uniqueness requirement that was preventing dashboards being deployed ([#241](https://github.com/databrickslabs/lsql/issues/241)). A fix has been implemented to address a uniqueness requirement issue with the dataset/widget name that was preventing dashboard deployment. A new `widget` instance is now created with a unique name, generated by appending `_widget` to the metadata ID, in the `get_layouts` method. This ensures that multiple widgets with the same ID but different content can exist in a single dashboard, thereby meeting the name uniqueness requirement. In the `save_to_folder` method, the widget name is modified by removing the `_widget` suffix before writing the textbox specification to a markdown file, maintaining consistency between the widget ID and file name. These changes are localized to the `get_layouts` and `save_to_folder` methods, and no new methods have been added. The existing functionality related to the creation, validation, and saving of dashboard layouts remains unaltered.
+
+
 ## 0.7.3
 
 * Added publish flag to `Dashboards.create_dashboard` ([#233](https://github.com/databrickslabs/lsql/issues/233)). In this release, we have added a `publish` flag to the `Dashboards.create_dashboard` method, allowing users to publish the dashboard upon creation, thereby resolving issue [#219](https://github.com/databrickslabs/lsql/issues/219). This flag is included in the `labs.yml` file with a description of its functionality. Additionally, the `no-open` flag's description has been updated to specify that it prevents the dashboard from opening in the browser after creation. The `create_dashboard` function in the `cli.py` and `dashboards.py` files has been updated to include the new `publish` flag, allowing for more flexibility in how users create and manage their dashboards. The `Dashboards.create_dashboard` method now calls the `WorkspaceClient.lakeview.publish` method when the `publish` flag is set to `True`, which publishes the created dashboard. This behavior is covered in the updated tests for the method.

src/databricks/labs/lsql/__about__.py

@@ -1 +1 @@
-__version__ = "0.7.3"
+__version__ = "0.7.4"