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

Undocumented breaking changes #432

Merged
merged 4 commits into from
Jun 23, 2019
Merged

Conversation

madsmtm
Copy link
Member

@madsmtm madsmtm commented Jun 23, 2019

I've changed my mind since #419, #406 and #405, I believe all undocumented items should be considered private per default. The reason is mostly that without this, it'll be very hard for me to make further internal improvements (especially Client.req_url is annoying).

In the future, I'll explicitly document what is considered a breaking change, but for now, I'll "cheat" a little.

madsmtm added 4 commits June 23, 2019 17:38
The file, and contained functions, were explicitly documented as something you couldn't rely on for backwards compatibility
Undocumented
@madsmtm madsmtm self-assigned this Jun 23, 2019
@madsmtm madsmtm merged commit b159f04 into master Jun 23, 2019
@madsmtm madsmtm deleted the undocumented-breaking-changes branch June 23, 2019 15:51
@madsmtm madsmtm restored the undocumented-breaking-changes branch June 23, 2019 15:59
madsmtm added a commit that referenced this pull request Jun 23, 2019
- Removed / privatized a lot of undocumented functionality, which might break some users application if they were relying on those (hence the minor version bump). See #432 for further reasoning
- Add `Client.forwardAttachment` and `Message.forwarded` attribute, see #420
- Fix parsing subattachments with no target, see #412
- Lots of other refactoring, aka. work on the transition towards v2
@madsmtm madsmtm deleted the undocumented-breaking-changes branch June 26, 2019 21:34
@chelsybradley15 chelsybradley15 linked an issue Mar 25, 2023 that may be closed by this pull request
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.

Screenshot (Mar 25, 2023 6:10:08 AM)
1 participant