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

chore: create @signalk/plugin-config package within same git project #521

Merged
merged 10 commits into from
Apr 24, 2018

Conversation

webmasterkai
Copy link
Contributor

Move plugin-config to /packages/plugin-config. This makes it easier for this github repo to be used as a "monorepo" and for plugin-config to be its own npm module.

Since plugin-config is its own module it should have its own ignore files. This removes old rules from the root and adds them to packages/plugin-config directory.

Move makes it easier for this github repo to be used as a monorepo and for plugin-config to be its own npm module.
Since plugin-config is its own module it should have its own ignore files. This removes old rules from root and adds them to plugin-config directory.
Need to change way we get path of the plugin-config assets. Using get-installed-path makes it easy. Server now works with plugin-config as package.
@webmasterkai webmasterkai changed the title chore: WIP - Monorepo plugin-config chore: Monorepo plugin-config Apr 23, 2018
I forgot to leave a comment of what the function does.
@webmasterkai
Copy link
Contributor Author

This is ready to review. Server changed the way we get the public path of for plugin-config assets. Using new get-installed-path dependency makes it easy. Server now works with plugin-config as a package. In prep for the future I created /lib/config/get/getPluginConfigPublic() that returns needed path.

Script to compile main.js before publishing npm module.
When plugin-config is a package the build process is not required.
@webmasterkai
Copy link
Contributor Author

References to the plugin-config build process have been removed. As a package it is no longer required.

@sbender9
Copy link
Member

I don't think we need this get code. You can just use app.config.appPath

@webmasterkai
Copy link
Contributor Author

Where would we use app.config.appPath?

@sbender9
Copy link
Member

On second thought. Lets keep it.

@sbender9
Copy link
Member

Can you come up with a better title. Something will make more sense to a layman in the CHANGELOG

@webmasterkai webmasterkai changed the title chore: Monorepo plugin-config chore: create @signalk/plugin-config package within same git project Apr 24, 2018
Do not want to install extra packages when folks npm install the plugin-config package.
@sbender9 sbender9 merged commit dcd0c9c into SignalK:master Apr 24, 2018
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.

2 participants