Skip to content

Conversation

psychedelicious
Copy link
Collaborator

Summary

Improves how ui_type deprecations are handled.

Related Issues / Discussions

Improvement on changes in #8577

QA Instructions

@JPPhoto I expect this change to give you 1) many more warnings and 2) better warnings

Merge Plan

n/a

Checklist

  • The PR has a short but descriptive title, suitable for a changelog
  • Tests added / updated (if applicable)
  • ❗Changes to a redux slice have a corresponding migration
  • Documentation added / updated (if applicable)
  • Updated What's New copy (if doing a release after this PR)

@github-actions github-actions bot added python PRs that change python files invocations PRs that change invocations frontend PRs that change frontend files labels Sep 19, 2025
@psychedelicious psychedelicious enabled auto-merge (rebase) September 19, 2025 12:08
- Move migration of model-specific ui_types into BaseInvocation. This
gives us access to the node and field names, so the warnings are more
useful to the end user.
- Ensure we serialize the fields' json_schema_extra with enum values.
This wasn't a problem until now, when it interferes with migrating
ui_type cleanly. It's a transparent change.
- Improve warnings when validating fields (which includes the ui_type
migration logic)
@psychedelicious psychedelicious force-pushed the psyche/feat/nodes/better-uitype-deprecations branch from d62855f to 8d26230 Compare September 19, 2025 12:08
@psychedelicious psychedelicious merged commit 3cec06f into main Sep 19, 2025
13 checks passed
@psychedelicious psychedelicious deleted the psyche/feat/nodes/better-uitype-deprecations branch September 19, 2025 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
frontend PRs that change frontend files invocations PRs that change invocations python PRs that change python files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants