Skip to content

fix(ng-add): inserted dependencies should be sorted #12847

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

Merged
merged 2 commits into from
Aug 27, 2018

Conversation

devversion
Copy link
Member

  • In case someone runs ng add @angular/material, all required dependencies are just inserted at the end of the dependencies object. We should sort the dependencies after adding dependencies.

* In case someone runs `ng add @angular/material`, all required dependencies are just inserted at the end of the `dependencies` object. We should sort the dependencies after adding dependencies.
@devversion devversion added pr: merge safe target: major This PR is targeted for the next major release labels Aug 27, 2018
@devversion devversion requested a review from amcdnl as a code owner August 27, 2018 10:14
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 27, 2018
@@ -8,19 +8,24 @@

import {Tree} from '@angular-devkit/schematics';

/** Function that sorts the keys of the specified object and returns the result as a new object. */
const sortObjectByKeys = (obj: any) => Object.keys(obj).sort()
.reduce((result, key) => (result[key] = obj[key]) && result, {});
Copy link
Member

Choose a reason for hiding this comment

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

  • Define this using the function keyword
  • I think you can use the object type here
  • Function description should start with the verb:
/**
 * Sorts the keys of the given object.
 * @returns A new object instance with sorted keys
 */

Copy link
Member Author

@devversion devversion Aug 27, 2018

Choose a reason for hiding this comment

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

Done. I did it like that because I wanted to somehow make clear that this isn't really part of the package-json functions. But seems like not having the export modifier is already clear enough.

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 27, 2018
@jelbourn jelbourn merged commit 0760dad into angular:master Aug 27, 2018
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants