Skip to content

Conversation

@Blaapje
Copy link

@Blaapje Blaapje commented Nov 3, 2020

This brings all dependencies to recent versions, closing #21

@Blaapje Blaapje marked this pull request as draft November 3, 2020 14:13
@Blaapje Blaapje marked this pull request as ready for review November 3, 2020 14:14
Copy link
Owner

@pbeshai pbeshai left a comment

Choose a reason for hiding this comment

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

Hi, thanks for your efforts on this. Can you please undo all the formatting changes you put in? They make it hard to see what actual changes were necessary for this version upgrade. Ideally we can just support a wider list of dependency versions without requiring a breaking change, but it's not clear to me what parts of the code needed to be changed for this to work.

@Blaapje
Copy link
Author

Blaapje commented Nov 5, 2020

Should be ok now, can you please review?

@Blaapje Blaapje requested a review from pbeshai November 5, 2020 12:04
Copy link
Owner

@pbeshai pbeshai left a comment

Choose a reason for hiding this comment

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

Still seeing a lot of formatting changes. I'll add prettier separately so this isn't an issue in the future, but for this PR I'd prefer that it be kept to just the required changes. You should be able to modify the file and save without applying formatting in your editor. Besides the formatting, just one minor question about the counter increment and we should be good to go with what looks like a minor version bump (I'll do this post merge).

.attr('id', `d3-line-chunked-clip-${chunkName}-${counter++}`);
.attr('id', `d3-line-chunked-clip-${chunkName}-${counter}`);
}
counter += 1;
Copy link
Owner

Choose a reason for hiding this comment

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

Why move the counter increment outside of the if statement?

Copy link
Author

Choose a reason for hiding this comment

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

Good question, it's not that I have any preference personally but the eslint test enforces this. The tests fail otherwise.

chunks.forEach((chunkName) => {
const chunkDef = chunkDefinitions[chunkName] || {};
const evaluatedChunk = {
styles: Object.assign({},
Copy link
Owner

Choose a reason for hiding this comment

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

Why bother changing this to not use Object.assign?

Copy link
Author

Choose a reason for hiding this comment

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

Again, no personal preference, but this is eslint enforced.

const undefinedLineClass = '.d3-line-chunked-undefined';
const definedPointClass = '.d3-line-chunked-defined-point';

function getDocument() {
Copy link
Owner

Choose a reason for hiding this comment

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

Thanks for updating these

Copy link
Author

@Blaapje Blaapje left a comment

Choose a reason for hiding this comment

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

All the formatting changes are because eslint was complaining about them and causing the module not to pass testing. If you really want we can drop the formatting commit, together with the linting stage (see package.json, line 27).

@pbeshai pbeshai merged commit 846f71c into pbeshai:master Nov 9, 2020
@pbeshai
Copy link
Owner

pbeshai commented Nov 9, 2020

Thanks for this, sorry for the outdated eslint config and lack of prettier

@pbeshai pbeshai mentioned this pull request Nov 9, 2020
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.

2 participants