Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
exclude
flag has been added to the configuration file for our lab tool, allowing users to specify a path to exclude from formatting during lab execution. This release also includes corrections to grammatical errors in the descriptions of existing flags related to catalog and database settings, such as updatingseperated
to "separate". Additionally, the flag descriptions forpublish
andopen-browser
have been updated for clarification:publish
now clearly controls whether the dashboard is published after creation, whileopen-browser
controls whether the dashboard is opened in a web browser. These changes are aimed at improving user experience and ease of use for our lab tool._row_to_sql
method of thebackends.py
file. Additionally, we have made updates to the_schema_for
method to use a new_field_type
class method. This change resolves a rare problem where thefield.type
is a string instead of a type and ensures compatibility with a pull request from an external repository (Added storage for direct filesystem references in code ucx#2526). The new_field_type
method attempts to load the type from__builtins__
if it's a string and logs a warning if it fails. The_row_to_sql
method now consistently uses the_field_type
method to get the field type. This ensures that the library functions seamlessly and consistently, avoiding any potential issues in the future.