Skip to content

attempt to fix foundational issue in stubs #249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 18, 2023
Merged

Conversation

zzzeek
Copy link
Member

@zzzeek zzzeek commented Jan 17, 2023

In the second revision of stubs, way in the beginning, if I'm reading correctly this commit: b7f469c, the basemost class of QueryableAttribute got lost. Since then, Mapped and QueryableAttribute have been treated as Any. All the revs of the plugin, the stubs, etc. have been based off this erroneous assumption. It's likely too late to change it
as it would introduce a lot of new risk. however, let's put
up a patch that's passing for the SQLAlchemy side, with some
mypy plugin changes on that end (yikes), then see if we can
get this side working, then look at what we have.

Description

Checklist

This pull request is:

  • A documentation / typographical error fix
    • Good to go, no issue or tests are needed
  • A short code fix
    • please include the issue number, and create an issue if none exists, which
      must include a complete example of the issue. one line code fixes without an
      issue and demonstration will not be accepted.
    • Please include: Fixes: #<issue number> in the commit message
    • please include tests. one line code fixes without tests will not be accepted.
  • A new feature implementation
    • please include the issue number, and create an issue if none exists, which must
      include a complete example of how the feature would look.
    • Please include: Fixes: #<issue number> in the commit message
    • please include tests.

Have a nice day!

@zzzeek zzzeek force-pushed the fix_queryable_attribute branch 2 times, most recently from 146cade to a908a42 Compare January 17, 2023 01:47
@CaselIT
Copy link
Member

CaselIT commented Jan 17, 2023

the changes look ok. I can move them into #237 while targeting 1_4 and not another branch

@zzzeek
Copy link
Member Author

zzzeek commented Jan 17, 2023

I thought maybe we can put "Any" at the base of QueryableAttribute , with these changes, then release, so that we can incrementally get this out. The mypy plugin changes I am hoping can be released without needing these stub changes at all, so that we can first see if they break anything on their own. mypy plugins are total dark magic

@CaselIT
Copy link
Member

CaselIT commented Jan 17, 2023

In case it's needed releasing the stubs is very easy and we can do that multiple times a day without much trouble

@zzzeek zzzeek force-pushed the fix_queryable_attribute branch 2 times, most recently from 8ef2f7a to b4ba6c9 Compare January 18, 2023 16:47
@zzzeek zzzeek force-pushed the fix_queryable_attribute branch from b4ba6c9 to 7eb78de Compare January 18, 2023 16:55
@CaselIT
Copy link
Member

CaselIT commented Jan 18, 2023

let's merge this then I'll rebase the other change to see if there is anything else

@CaselIT CaselIT merged commit aeb8785 into main Jan 18, 2023
@CaselIT CaselIT deleted the fix_queryable_attribute branch January 18, 2023 19:35
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.

2 participants