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

feat(Teams): backport support for teams #3357

Merged
merged 5 commits into from Jul 11, 2019

Conversation

SpaceEEC
Copy link
Member

Please describe the changes this PR makes and why it should be merged:
This PR backports #3350 (a22aabf) in a semver-minor manner.
(Namingly adding a team property opposed to replacing owner)

Status

  • Code changes have been tested against the Discord API, or there are no code changes
  • I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

  • This PR changes the library's interface (methods or parameters added)
    • This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
  • This PR only includes non-code changes, like changes to documentation, README, etc.

Copy link
Contributor

@bdistin bdistin left a comment

Choose a reason for hiding this comment

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

otherwise lgtm

* The owning team of this OAuth application
* @type {?Team}
*/
this.team = new Team(this.client, data.team);
Copy link
Contributor

Choose a reason for hiding this comment

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

The team property should always exist as null or Team, not excluding the property if no data.team, so the object keeps consistent shape.

Copy link
Contributor

Choose a reason for hiding this comment

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

Well, and also, it should be deprecated since it will be gone in v12.

Copy link
Member Author

@SpaceEEC SpaceEEC Jun 27, 2019

Choose a reason for hiding this comment

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

How would such a deprecation look like? Emitting a process warning on access seems unjustified as there is no way to fix this before v12. Maybe a warn or info in the documentation?

Copy link
Contributor

Choose a reason for hiding this comment

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

At minimum just a docstring @deprecated. But probably that with an explanation (in a warn or info tag) in the description.

@SpaceEEC SpaceEEC merged commit 0cd7556 into discordjs:11.5-dev Jul 11, 2019
@SpaceEEC SpaceEEC deleted the feat/teams branch July 11, 2019 11:10
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.

None yet

2 participants