-
Notifications
You must be signed in to change notification settings - Fork 13
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
chore(hub-teams): remove pre 9.1 well known teams #561
Conversation
Codecov Report
@@ Coverage Diff @@
## master #561 +/- ##
===========================================
Coverage 100.00% 100.00%
===========================================
Files 88 428 +340
Lines 1314 6000 +4686
Branches 193 945 +752
===========================================
+ Hits 1314 6000 +4686
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good - only ask is to make the source of deprecation warnings more obvious.. like Hub.js::<functionName> Deprecation warning <details>
? PRE_9_1_WELLKNOWNTEAMS | ||
: WELLKNOWNTEAMS; | ||
/* tslint:disable no-console */ | ||
console.warn("portalApiVersion is deprecated and will be removed at v9.0.0"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add the function name to the warning... otherwise, it's hard to know where this is coming from
? PRE_9_1_WELLKNOWNTEAMS | ||
: WELLKNOWNTEAMS; | ||
/* tslint:disable no-console */ | ||
console.warn("portalApiVersion is deprecated and will be removed at v9.0.0"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here
Description:
Removes pre 9.1 well known teams
Instructions for testing:
Screenshot/GIF:
Closes Issues: # (if appropriate)
ran commit script (
npm run c
)Note If you don't run the commit script at least once, the Semantic Pull Request check will fail. Save yourself some time, and run
npm run c
and follow the prompts.For more information see the README