Skip to content

chore: IntoSchema overhaul#3262

Closed
FBruzzesi wants to merge 1 commit intomainfrom
chore/into-schema-overhaul
Closed

chore: IntoSchema overhaul#3262
FBruzzesi wants to merge 1 commit intomainfrom
chore/into-schema-overhaul

Conversation

@FBruzzesi
Copy link
Copy Markdown
Member

What type of PR is this? (check all applicable)

  • 💾 Refactor
  • ✨ Feature
  • 🐛 Bug Fix
  • 🔧 Optimization
  • 📝 Documentation
  • ✅ Test
  • 🐳 Other

Related issues

Checklist

  • Code follows style guide (ruff)
  • Tests added
  • Documented the changes

If you have comments or can explain your changes, please do so below

Opening as draft - I will follow up with a few more tests

@FBruzzesi FBruzzesi added enhancement New feature or request typing labels Oct 31, 2025
@FBruzzesi
Copy link
Copy Markdown
Member Author

FML, I didn't realize these changes are completely incompatible with #3252

Will think about it more calmly

@MarcoGorelli
Copy link
Copy Markdown
Member

ooh so sorry 🙈

@dangotbanned
Copy link
Copy Markdown
Member

#3262 (comment)

@FBruzzesi I think if you were looking to clean things up following #3252, then #2486 may be what we're missing?

/,
*,
context: _LimitedContext,
schema: IntoSchema | None,
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that if every one of these constructors is going to now require Schema, then we shouldn't return a dict from:

  • CompliantFrame.schema (and friends)

I understand that these changes make things cleaner inside the methods, but the classes as a whole are now less-ergonomic 🤔

Copy link
Copy Markdown
Member

@dangotbanned dangotbanned Oct 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm bringing this up since from the perspective of plugins, this is an API break. on second read, that was a bit strong 🫣

We've already established that is expected for now, but I'd rather we get the consistency right in one swoop 🙂

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok that's fair! I will address the original issue and a bit more, but not too much else 😂

@FBruzzesi
Copy link
Copy Markdown
Member Author

Closing in favor of #3266

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request typing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

typing.IntoSchema too narrow

3 participants