Skip to content

Commit 6a1016f

Browse files
committed
chore(release): bump to v0.29.1
1 parent d7ce1c2 commit 6a1016f

File tree

3 files changed

+22
-3
lines changed

3 files changed

+22
-3
lines changed

docs/changelog.rst

+19
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,25 @@
33
0.x Changelog
44
=============
55

6+
.. changelog:: 0.29.1
7+
:date: 2025-01-17
8+
9+
.. change:: add convenience hooks for `to_model` operations
10+
:type: feature
11+
:pr: 347
12+
13+
The service layer has always has a `to_model` function that accepts data and optionally an operation name. It would return a SQLAlchemy model no matter the input you gave it.
14+
15+
It is possible to move business logic into this `to_model` layer for populating fields on insert. (i.e. slug fields or tags, etc.).
16+
17+
When having logic for `insert`, `update`, `delete`, and `upsert`, that function can be a bit overwhelcoming. Now, there are helper functions that you can use that is specific to each DML hook:
18+
19+
* `to_model_on_create`
20+
* `to_model_on_update`
21+
* `to_model_on_delete`
22+
* `to_model_on_upsert`
23+
24+
625
.. changelog:: 0.29.0
726
:date: 2025-01-17
827

pyproject.toml

+2-2
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ maintainers = [
4747
name = "advanced_alchemy"
4848
readme = "README.md"
4949
requires-python = ">=3.8"
50-
version = "0.29.0"
50+
version = "0.29.1"
5151

5252
[project.urls]
5353
Changelog = "https://docs.advanced-alchemy.litestar.dev/latest/changelog"
@@ -168,7 +168,7 @@ test = [
168168
allow_dirty = true
169169
commit = true
170170
commit_args = "--no-verify"
171-
current_version = "0.29.0"
171+
current_version = "0.29.1"
172172
ignore_missing_files = false
173173
ignore_missing_version = false
174174
message = "chore(release): bump to v{new_version}"

uv.lock

+1-1
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)