Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pre-commit.ci] pre-commit autoupdate #826

Merged
merged 3 commits into from
Jan 13, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .pre-commit-config.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ repos:
additional_dependencies: [numpy, types-requests]
exclude: tests/|docs/
- repo: https://github.com/astral-sh/ruff-pre-commit
rev: v0.8.6
rev: v0.9.1
hooks:
- id: ruff
args: [--fix, --exit-non-zero-on-fix]
2 changes: 2 additions & 0 deletions docs/contributing.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,7 @@ We recommend using the button "Generate release notes" to automatically collect
The release notes serve as a changelog for the user of the package so it's important to have them curated and well-organized. This is explained in depth below.

Here is an example of automatically generated release notes for a previous release (v0.2.3):

```
## What's Changed
* Add clip parameter to polygon_query; tests missing by @LucaMarconato in https://github.com/scverse/spatialdata/pull/670
Expand Down Expand Up @@ -172,6 +173,7 @@ The release notes above can be hard to read, but this is addressed by our [confi
Use informative titles for PRs, as these will serve as section titles in the release notes (rename the PRs if necessary). You can also manually edit the release notes before publishing them to improve readability.

Some additional considerations

- Important! If a PR is large and its title isn't informative or requires multiple lines, **do not** add a release tag. Instead, in the first message of the PR discussion, please include a markdown section with a brief description of the intended release notes. This will allow the person making a release to manually add the PR content to the release notes during the release process.
- Please avoid redundancy and do not add the same release notes to consecutive pre-releases/releases/post-releases.
- When automatically generating the release notes, you can use the button "Previous tag: ..." to choose which PRs will be included in the release notes.
Expand Down
7 changes: 3 additions & 4 deletions src/spatialdata/_core/spatialdata.py
Original file line number Diff line number Diff line change
Expand Up @@ -1680,10 +1680,9 @@ def get_attrs(

Returns
-------
dict[str, Any] | str | pd.DataFrame
The data associated with the specified key, returned in the specified format.
The format can be a dictionary, JSON string, or Pandas DataFrame, depending on
the value of `return_as`.
The data associated with the specified key, returned in the specified format.
The format can be a dictionary, JSON string, or Pandas DataFrame, depending on
the value of `return_as`.
"""

def _flatten_mapping(m: Mapping[str, Any], parent_key: str = "", sep: str = "_") -> dict[str, Any]:
Expand Down
Loading