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

Splits the project into core and cli modules #101

Merged
merged 3 commits into from
Feb 12, 2020

Conversation

andreban
Copy link
Member

  • Uses lerna to manage modules
  • Adds README.md for each module
  • Updates version to 0.4.0

- Uses `lerna` to manage modules
- Adds README.md for each module
- Updates version to 0.4.0
@andreban andreban force-pushed the split-modules-lerna branch from ed48b87 to d9a0241 Compare February 11, 2020 16:47
README.md Outdated
validate your domain. The
[TWA Quick Start Guide](https://developers.google.com/web/updates/2019/08/twas-quickstart#creating-your-asset-link-file)
explains how to extract the information needed to generate it.
- **[llama-pack-core](./packages/core):** a javascript library that for generating, building and
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: remove "that"

explains how to extract the information needed to generate it.
- **[llama-pack-core](./packages/core):** a javascript library that for generating, building and
updating TWA projects.
- **[llama-pack-cli](./packages/cli):** a command-line version for llama-pack.
Copy link
Collaborator

Choose a reason for hiding this comment

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

A command-line "version" sounds a bit odd.

"llama-pack core wrapped for the command line" maybe?

Copy link
Member Author

Choose a reason for hiding this comment

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

"command-line interface for llama-pack"?

},
"devDependencies": {
"@typescript-eslint/eslint-plugin": "^2.9.0",
"@typescript-eslint/parser": "^2.9.0",
"eslint": "^6.6.0",
"eslint-config-google": "^0.14.0",
"jasmine": "^3.5.0"
"jasmine": "^3.5.0",
Copy link
Collaborator

@PEConn PEConn Feb 12, 2020

Choose a reason for hiding this comment

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

So there are tests in the parent package?

Copy link
Member Author

@andreban andreban Feb 12, 2020

Choose a reason for hiding this comment

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

We don't. Cleaned-up the dependencies in root. We can re-add later if we end up needing.

import {AndroidSdkTools} from './lib/androidSdk/AndroidSdkTools';
import {Config} from './lib/Config';
import {GradleWrapper} from './lib/GradleWrapper';
import Log from './lib/Log';
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why no {}?

Copy link
Member Author

Choose a reason for hiding this comment

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

Log is using export default Log, while others simple use export. Maybe I should change Log to just use export, but likely in another PR.

@andreban andreban marked this pull request as ready for review February 12, 2020 17:40
@andreban andreban merged commit e83a4ee into GoogleChromeLabs:master Feb 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants