Skip to content
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

Merge Feature/v3 into main #254

Merged
merged 134 commits into from
Nov 27, 2023
Merged

Merge Feature/v3 into main #254

merged 134 commits into from
Nov 27, 2023

Conversation

EvieePy
Copy link
Member

@EvieePy EvieePy commented Nov 27, 2023

Description

Merge feature/v3 into main.
Version 3 will now become the stable release after merging.

Version 3 went through 16 BETA stages and 2 Release Candidate stages.
To the best of my knowledge all major bugs have been found, and this version should be considered fairly stable at this point.

Documentation is complete minus some minor QoL examples and recipes.

This version complies with pyright strict and no errors or warnings are currently being emitted.

Black has been ran over this version.

Checklist

  • If code changes were made then they have been tested.
    • I have updated the documentation to reflect the changes.
    • I have updated the changelog with a quick recap of my changes.
  • This PR fixes an issue.
  • This PR adds something new (e.g. new method or parameters).
  • This PR is a breaking change (e.g. methods or parameters removed/renamed)
  • This PR is not a code change (e.g. documentation, README, ...)
  • I have read and agree to the Developer Certificate of Origin for this contribution

Sachaa-Thanasius and others added 10 commits November 27, 2023 07:58
* More consistency with typing for py3.10+
- Using ruff and stricter pyright settings. Will have to remove later.

* Fix another union and eliminate an unnecessary cast.

* Revert pyproject.toml configuration.
- Leave two extra pyright settings on — they can't hurt, right?

* Incorporate feedback and also change filter payload imports to relative.
- Not as sure on the relative import change. In my opinion, this is a clearer indicator of where the imports are coming from, is more consistent with similar imports in other files, and doesn't run the risk of messing with an import of builtin types module, unlikely as that is to happen. Might be a matter of style though.

* More minor explicit type-aliasing.
@EvieePy EvieePy requested a review from chillymosh November 27, 2023 09:11
@EvieePy EvieePy added the 3.0 Wavelink Version 3 label Nov 27, 2023
Copy link
Contributor

@AbstractUmbra AbstractUmbra left a comment

Choose a reason for hiding this comment

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

Lots of work has gone into v3, very impressive.

Code changes and all other updates look good!

@EvieePy EvieePy changed the title Feature/v3 Merge Feature/v3 into main Nov 27, 2023
@EvieePy EvieePy merged commit 0af9204 into main Nov 27, 2023
4 checks passed
@EvieePy EvieePy deleted the feature/v3 branch November 27, 2023 21:30
@chillymosh
Copy link
Contributor

LGTM

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