Skip to content

Conversation

@sendilkumarn
Copy link
Member

What kind of change does this PR introduce?

bugfix

Did you add tests for your changes?
Yes
If relevant, did you update the documentation?
NA

Summary
Fixes #159

Does this PR introduce a breaking change?

Other information

@webpack-bot
Copy link

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

Copy link
Member

@evenstensberg evenstensberg left a comment

Choose a reason for hiding this comment

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

Lgtm here, @fokusferit @ematipico PTAL


const fitOptionsToUse = p => {
let options;
p.value.properties.map(prop => {
Copy link
Contributor

Choose a reason for hiding this comment

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

.map returns a new array. If you don't assign it, it's better to use .forEach.

prop => prop.key.name !== "options"
);

p.value.properties.map(prop => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Also here: .forEach is more appropriate

@webpack-bot
Copy link

@sendilkumarn Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@ematipico Please review the new changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Migrate] loaders transform: should options be always grouped with the loader

4 participants