Skip to content

feat: add content_field support to generic_resolver - #1002

Open
mhoff wants to merge 6 commits into
mainfrom
feat-generic-resolver-content-field
Open

feat: add content_field support to generic_resolver#1002
mhoff wants to merge 6 commits into
mainfrom
feat-generic-resolver-content-field

Conversation

@mhoff

@mhoff mhoff commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

Description

  • Briefly summarize your changes in a few bullet points (can and should correspond to CHANGELOG.md)
  • Relates to #XXX (insert issue number here), if there is a corresponding GH issue

Assignee

  • The changes adhere to the contribution guidelines
  • I have performed a self-review of my code
  • My changes generate no new warnings (e.g. flake8/mypy/pytest/...) other than deprecations

Documentation

Code Quality

  • Patch test coverage > 95% and does not decrease
  • New code uses correct & specific type hints

How did you verify that the changes work in practice?

  • List of (preferably easy reproducible) tests including OS

Reviewer


The rendered docs for this PR can be found here.

@mhoff
mhoff force-pushed the feat-generic-resolver-content-field branch from 895ca09 to 0f7ddc2 Compare July 30, 2026 09:29
@mhoff
mhoff force-pushed the feat-generic-resolver-content-field branch from 23e439c to 4c660fd Compare July 30, 2026 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant