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

[d3-scale-chromatic] Upgrade to v1.5.0 #43917

Merged
merged 1 commit into from
Apr 15, 2020
Merged

[d3-scale-chromatic] Upgrade to v1.5.0 #43917

merged 1 commit into from
Apr 15, 2020

Conversation

axelboc
Copy link
Contributor

@axelboc axelboc commented Apr 15, 2020

Please fill in this template.

  • Use a meaningful title for the pull request. Include the name of the package modified.
  • Test the change in your own code. (Compile and run.)
  • Add or edit tests to reflect the change. (Run with npm test.)
  • Follow the advice from the readme.
  • Avoid common mistakes.
  • Run npm run lint package-name (or tsc if no tslint.json is present).

Select one of these and delete the others:

If changing an existing definition:

  • Provide a URL to documentation or source code which provides context for the suggested changes: d3/d3-scale-chromatic@v1.3.2...v1.5.0
  • If this PR brings the type definitions up to date with a new version of the JS library, update the version number in the header.
  • Include tests for your changes
  • If you are making substantial changes, consider adding a tslint.json containing { "extends": "dtslint/dt.json" }. If for reason the any rule need to be disabled, disable it for that line using // tslint:disable-next-line [ruleName] and not for whole package so that the need for disabling can be reviewed.

@@ -12,7 +12,7 @@ import * as d3ScaleChromatic from 'd3-scale-chromatic';
// Preparatory Steps
// -----------------------------------------------------------------------

let colorInterpolator: ((t: number) => string);
let colorInterpolator: (t: number) => string;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is from running Prettier.

const Warm: string = d3ScaleChromatic.interpolateWarm(0.7);
const Cool: string = d3ScaleChromatic.interpolateCool(0.7);
const Rainbow: string = d3ScaleChromatic.interpolateRainbow(0.7);
const Sinebow: string = d3ScaleChromatic.interpolateSinebow(0.7);
const CubehelixDefault: string = d3ScaleChromatic.interpolateCubehelixDefault(0.7);
Copy link
Contributor Author

@axelboc axelboc Apr 15, 2020

Choose a reason for hiding this comment

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

I've re-ordered the interpolators in this section to match the type definitions and the library's README.

@typescript-bot
Copy link
Contributor

👋 Hi there! I’ve run some quick measurements against master and your PR. These metrics should help the humans reviewing this PR gauge whether it might negatively affect compile times or editor responsiveness for users who install these typings.

Let’s review the numbers, shall we?

Comparison details 📊
master #43917 diff
Batch compilation
Memory usage (MiB) 33.9 36.0 +6.2%
Type count 2181 2183 0%
Assignability cache size 147 149 +1%
Language service
Samples taken 440 458 +4%
Identifiers in tests 440 458 +4%
getCompletionsAtPosition
    Mean duration (ms) 59.3 59.2 -0.2%
    Mean CV 16.9% 16.4%
    Worst duration (ms) 85.6 87.3 +2.1%
    Worst identifier schemeYlOrRd schemeYlOrRd
getQuickInfoAtPosition
    Mean duration (ms) 57.3 56.2 -1.9%
    Mean CV 15.4% 14.7% -4.7%
    Worst duration (ms) 75.8 76.0 +0.3%
    Worst identifier Plasma d3ScaleChromatic

It looks like nothing changed too much. I won’t post performance data again unless it gets worse.

@typescript-bot typescript-bot added the Perf: Same typescript-bot determined that this PR will not significantly impact compilation performance. label Apr 15, 2020
@typescript-bot typescript-bot added this to Waiting for Reviewers in Pull Request Status Board Apr 15, 2020
@typescript-bot typescript-bot added Popular package This PR affects a popular package (as counted by NPM download counts). Awaiting reviewer feedback labels Apr 15, 2020
@typescript-bot
Copy link
Contributor

typescript-bot commented Apr 15, 2020

@axelboc Thank you for submitting this PR!

🔔 @Ledragon @gustavderdrache @borisyankov @henriquefm - please review this PR in the next few days. Be sure to explicitly select Approve or Request Changes in the GitHub UI so I know what's going on.

If no reviewer appears after a week, a DefinitelyTyped maintainer will review the PR instead.

@typescript-bot typescript-bot moved this from Waiting for Reviewers to Check and Merge in Pull Request Status Board Apr 15, 2020
@typescript-bot typescript-bot added Owner Approved A listed owner of this package signed off on the pull request. Merge:Express and removed Awaiting reviewer feedback labels Apr 15, 2020
@typescript-bot
Copy link
Contributor

A definition owner has approved this PR ⭐️. A maintainer will merge this PR shortly. If it shouldn't be merged yet, please leave a comment saying so and we'll wait. Thank you for your contribution to DefinitelyTyped!

@armanio123 armanio123 merged commit 88c95a5 into DefinitelyTyped:master Apr 15, 2020
Pull Request Status Board automation moved this from Check and Merge to Done Apr 15, 2020
@typescript-bot
Copy link
Contributor

I just published @types/d3-scale-chromatic@1.5.0 to npm.

@axelboc axelboc deleted the d3-scale-chromatic-1-5-0 branch April 16, 2020 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Owner Approved A listed owner of this package signed off on the pull request. Perf: Same typescript-bot determined that this PR will not significantly impact compilation performance. Popular package This PR affects a popular package (as counted by NPM download counts).
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants