Skip to content

Conversation

@QilongTang
Copy link
Contributor

Please Note:

  1. Before submitting the PR, please review How to Contribute to Dynamo
  2. Dynamo Team will meet 1x a month to review PRs found on Github (Issues will be handled separately)
  3. PRs will be reviewed from oldest to newest
  4. If a reviewed PR requires changes by the owner, the owner of the PR has 30 days to respond. If the PR has seen no activity by the next session, it will be either closed by the team or depending on its utility will be taken over by someone on the team
  5. PRs should use either Dynamo's default PR template or one of these other template options in order to be considered for review.
  6. PRs that do not have one of the Dynamo PR templates completely filled out with all declarations satisfied will not be reviewed by the Dynamo team.
  7. PRs made to the DynamoRevit repo will need to be cherry-picked into all the DynamoRevit Release branches that Dynamo supports. Contributors will be responsible for cherry-picking their reviewed commits to the other branches after a LGTM label is added to the PR.

Purpose

Cherry-picks #9352 to RC2.1.0 branch to prevent merge conflicts for people

Declarations

Check these if you believe they are true

  • The code base is in a better state after this PR
  • Is documented according to the standards
  • The level of testing this PR includes is appropriate
  • User facing strings, if any, are extracted into *.resx files
  • All tests pass using the self-service CI.
  • Snapshot of UI changes, if any.
  • Changes to the API follow Semantic Versioning, and are documented in the API Changes document.

Reviewers

FYIs

@mjkkirschner @alfarok @ColinDayOrg @aparajit-pratap @scottmitchell @reddyashish

@QilongTang QilongTang changed the title Remove and Sort Usings (#9352) [Cherry-pick] Remove and Sort Usings (#9352) Jan 2, 2019
@QilongTang
Copy link
Contributor Author

All checks passed, merging

@QilongTang QilongTang merged commit a371ce9 into RC2.1.0_master Jan 2, 2019
@QilongTang QilongTang deleted the RemoveAndSortUsings branch January 2, 2019 19:51
@aparajit-pratap
Copy link
Contributor

Wow, did you use Resharper to do this globally or did you remove them file by file manually?

@QilongTang
Copy link
Contributor Author

@aparajit-pratap ReSharper can do this but I used the alternative extension which is Productivity Power Tools for VS 2017 mentioned in https://stackoverflow.com/questions/283471/remove-unused-namespaces-across-a-whole-project-or-solution-at-once/35619794

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.

3 participants