Skip to content

test: verify correct typing of mixins #280

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

bradenmacdonald
Copy link
Contributor

This PR makes some simplifications to PublishableEntityMixin and PublishableEntityVersionMixin so that their subclasses like ComponentVersion automatically get the correct type on their objects class property, and don't have to override it to satisfy mypy. This will slightly simplify the code as we get more publishable entities in the near future (e.g. components and units).

I also got rid of the custom PublishableEntityMixinManager and PublishableEntityVersionMixinManager classes, replacing them with the reusable WithRelationsManager that does the same thing and which now supports generic typing properly.

New type-only tests are added to assert that the typing of the manager (objects) and its returned instances are correct.

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Feb 20, 2025
@openedx-webhooks
Copy link

Thanks for the pull request, @bradenmacdonald!

This repository is currently maintained by @axim-engineering.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.


Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

# interface as the base manager class.
objects: models.Manager[Component] = WithRelationsManager(
# Set up our custom manager. It has the same API as the default one, but selects related objects by default.
objects: ClassVar[WithRelationsManager[Component]] = WithRelationsManager( # type: ignore[assignment]
Copy link
Contributor Author

@bradenmacdonald bradenmacdonald Feb 20, 2025

Choose a reason for hiding this comment

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

Unfortunately this line still requires specifying the type explicitly and also needs ignore[assignment] because mypy for some reason thinks that WithRelationsManager[Component] and WithRelationsManager[Self] are different things in this case. Seems like a mypy bug 🤷🏻‍♂️.

In all other cases, where we're just using WithRelationsManager directly or just relying on a mixin to provide objects, no type annotations or suppression are needed. It's just here where the override in Component seems to conflict with the override in PublishableEntityMixin (though it shouldn't).


objects: models.Manager[PublishableEntityMixin] = PublishableEntityMixinManager()
# select these related entities by default for all queries
objects: ClassVar[WithRelationsManager[Self]] = WithRelationsManager(
Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's actually possible to remove this ClassVar[WithRelationsManager[Self]] annotation, and everything will still be correct. Though it seems VS Code / Pyright then interprets it as Manager[Self] rather than WithRelationsManager[Self], whereas mypy is unaffected. I don't have a strong opinion but it seems fine to be more explicit.

@mphilbrick211
Copy link

Friendly ping on this, @ormsbee :)

@bradenmacdonald
Copy link
Contributor Author

This was mostly included in #278 . Now the only new thing here are some tests to verify that the typing is correct.

@bradenmacdonald bradenmacdonald changed the title refactor: improve typing of mixins test: verify correct typing of mixins Mar 14, 2025
@bradenmacdonald bradenmacdonald force-pushed the braden/mypy-objects branch 2 times, most recently from 7f8afba to a56fbc5 Compare March 14, 2025 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
open-source-contribution PR author is not from Axim or 2U
Projects
Status: Ready for Review
Development

Successfully merging this pull request may close these issues.

3 participants