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

Cleanup for #229 #300

Merged
merged 2 commits into from Jun 18, 2018
Merged

Cleanup for #229 #300

merged 2 commits into from Jun 18, 2018

Conversation

@RyanJarv
Copy link
Contributor

RyanJarv commented Jun 7, 2018

Few things to clean up post #229 merge

  • Fix yarn run sync --<project>_ref= command
  • Set build target through the config for create_dist
  • Check config.gClientVerbose directly and remove unused options
  • buildMuon
    • Renamed to buildTarget
    • Now uses build target set in config

Submitter Checklist:

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Ran git rebase -i to squash commits (if needed).
  • Tagged reviewers and labelled the pull request as needed.

Test Plan:

Just manually right now across various machines (which is likely why so many bugs are getting missed here). Have this ticket open for adding testing to the build tools in general #304.

Reviewer Checklist:

  • New files have MPL-2.0 license header.
  • Request a security/privacy review as needed.
  • Adequate test coverage exists to prevent regressions
@RyanJarv RyanJarv requested a review from bridiver Jun 7, 2018
RyanJarv added 2 commits Jun 6, 2018
* Set build target through the config for create_dist
* check config.gClientVerbose directly
* change lib/util methood buildMuon to buildCore
Was supposed to be fixed in #229 but lost a few commits. We fix
the snakecasing done by commander.js there but don't set
the ref correctly because the name differs from what is set
by lib/config.js. This adds a parameter to the projects
config to specify what should be used for the command line
arg (defaults to name.replace('-', '_').

Fixes #299
@RyanJarv RyanJarv force-pushed the RyanJarv:fixup branch from de7fd0b to 889b15e Jun 7, 2018
@RyanJarv RyanJarv self-assigned this Jun 7, 2018
@RyanJarv RyanJarv requested a review from bkero Jun 8, 2018
@RyanJarv RyanJarv changed the title [WIP] Cleanup for #229 Cleanup for #229 Jun 12, 2018
@RyanJarv
Copy link
Contributor Author

RyanJarv commented Jun 12, 2018

@bridiver you mind taking a look at this?

@RyanJarv RyanJarv requested a review from mbacchi Jun 13, 2018
@RyanJarv RyanJarv mentioned this pull request Jun 18, 2018
3 of 9 tasks complete
@@ -176,7 +176,8 @@ Config.prototype.buildProjects = function () {
url: getNPMConfig(['projects', projectName, 'repository', 'url']),
gclientName: getNPMConfig(['projects', projectName, 'dir']),
dir: path.join(this.rootDir, getNPMConfig(['projects', projectName, 'dir'])),
custom_deps: packages.config.projects[projectName].custom_deps
custom_deps: packages.config.projects[projectName].custom_deps,
arg_name: projectName.replace('-', '_')

This comment has been minimized.

Copy link
@bridiver

bridiver Jun 18, 2018

Collaborator

maybe just name? arg_ was a little confusing to me. Just a nit though.

This comment has been minimized.

Copy link
@RyanJarv

RyanJarv Jun 18, 2018

Author Contributor

Didn't want it to get confused with the actual name since the original name is still being used in other places

@RyanJarv RyanJarv merged commit 6c4275c into brave:master Jun 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.