Releases: strawberry-graphql/strawberry-sqlalchemy
🍓 0.8.0
Added a new optional constructor parameter to always use lists instead of relay Connections for relationships. Defaults to False, maintaining current functionality. If set to True, all relationships will be handled as lists.
Example:
mapper = StrawberrySQLAlchemyMapper(always_use_list=True)
Releases contributed by @gabor-lbl via #257
Contributors
Assets 4
🍓 0.7.0
Implement Relay-style cursor pagination for SQLAlchemy relationships by extending the connection resolver and DataLoader to accept pagination arguments, computing pageInfo metadata, and introducing cursor utilities. Add PaginatedLoader to scope DataLoader instances per pagination parameters and update tests to verify pagination behavior.
New Features:
- Support cursor-based pagination (first, after, last, before) on GraphQL relationship fields
- Introduce PaginatedLoader to manage DataLoader instances per pagination configuration
Enhancements:
- Extend connection resolvers to compute pageInfo fields (hasNextPage, hasPreviousPage, totalCount) and handle forward and backward pagination
- Add utilities for cursor encoding/decoding and relationship key extraction
Tests:
- Add comprehensive tests for forward and backward pagination scenarios in both synchronous and asynchronous execution contexts
Examples:
Get the first three books for a specific author:
query {
author(id: 1) {
id
name
books(first: 3) {
edges {
node {
id
title
}
}
pageInfo {
hasNextPage
hasPreviousPage
startCursor
endCursor
}
}
}
}Get all books after a specific book's cursor:
query($afterBook: String) {
author(id: 1) {
id
name
books(after: $afterBook) {
edges {
node {
id
title
}
}
pageInfo {
hasNextPage
hasPreviousPage
startCursor
endCursor
}
}
}
}Get the first three books for a specific author after a specific book's cursor:
query($afterBook: String) {
author(id: 1) {
id
name
books(first: 3, after: $afterBook) {
edges {
node {
id
title
}
}
pageInfo {
hasNextPage
hasPreviousPage
startCursor
endCursor
}
}
}
}Get the last three books for a specific author:
query {
author(id: 1) {
id
name
books(last: 3) {
edges {
node {
id
title
}
}
pageInfo {
hasNextPage
hasPreviousPage
startCursor
endCursor
}
}
}
}Get all books before a specific book's cursor:
query($beforeBook: String) {
author(id: 1) {
id
name
books(before: $beforeBook) {
edges {
node {
id
title
}
}
pageInfo {
hasNextPage
hasPreviousPage
startCursor
endCursor
}
}
}
}Get the last three books for a specific author before a specific book's cursor:
query($beforeBook: String) {
author(id: 1) {
id
name
books(last: 3, before: $beforeBook) {
edges {
node {
id
title
}
}
pageInfo {
hasNextPage
hasPreviousPage
startCursor
endCursor
}
}
}
}Releases contributed by @davidroeca via #255
Contributors
Assets 4
🍓 0.6.4
This release improves how types inherit fields from other mapped types using @mapper.type(...).
You can now safely inherit from another mapped type, and the resulting GraphQL type will include all expected fields with predictable conflict resolution.
Some examples:
- Basic Inheritance:
@mapper.type(ModelA)
class ApiA:
pass
@mapper.type(ModelB)
class ApiB(ApiA):
# ApiB inherits all fields declared in ApiA
pass- The
__exclude__option continues working:
@mapper.type(ModelA)
class ApiA:
__exclude__ = ["relationshipB_id"]
@mapper.type(ModelB)
class ApiB(ApiA):
# ApiB will have all fields declared in ApiA, except "relationshipB_id"
pass- If two SQLAlchemy models define fields with the same name, the field from the model inside
.type(...)takes precedence:
class ModelA(base):
__tablename__ = "a"
id = Column(String, primary_key=True)
example_field = Column(String(50))
class ModelB(base):
__tablename__ = "b"
id = Column(String, primary_key=True)
example_field = Column(Integer, autoincrement=True)
@mapper.type(ModelA)
class ApiA:
# example_field will be a String
pass
@mapper.type(ModelB)
class ApiB(ApiA):
# example_field will be taken from ModelB and will be an Integer
pass- If a field is explicitly declared in the mapped type, it will override any inherited or model-based definition:
class ModelA(base):
__tablename__ = "a"
id = Column(String, primary_key=True)
example_field = Column(String(50))
class ModelB(base):
__tablename__ = "b"
id = Column(String, primary_key=True)
example_field = Column(Integer, autoincrement=True)
@mapper.type(ModelA)
class ApiA:
pass
@mapper.type(ModelB)
class ApiB(ApiA):
# example_field will be a Float
example_field: float = strawberry.field(name="exampleField")Contributors
Assets 4
🍓 0.6.3
Contributors
Assets 4
🍓 0.6.2
This release does not introduce any new features or bug fixes. It focuses solely on internal code quality improvements.
Changes:
- Added Mypy configuration aligned with the main Strawberry project.
- Enforced type checking via CI to ensure consistency.
- Ran pre-commit across all files to standardize formatting and follow the project's linting architecture.
These changes aim to improve maintainability and ensure better development practices moving forward.
Contributors
Assets 4
🍓 0.6.1
Ensure association proxy resolvers return valid relay connections, including page_info and edge cursor details, even for empty results.
Thanks to https://github.com/tylernisonoff for the original PR.
Contributors
Assets 4
🍓 0.6.0
Added support for GraphQL directives in the SQLAlchemy type mapper, enabling better integration with GraphQL federation.
Example usage:
@mapper.type(Employee, directives=["@deprecated(reason: 'Use newEmployee instead')"])
class Employee:
passReleases contributed by @csechrist via #204
Contributors
Assets 4
🍓 0.5.0
Add an optional function to exclude relationships from relay pagination and use traditional strawberry lists.
Default behavior preserves original behavior for backwords compatibilty.
Releases contributed by @fruitymedley via #168