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.

Sign up for GitHub

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

Jump to bottom

Establish naming convention for provider plugins #1

Open
pmuens opened this issue Nov 11, 2016 · 1 comment
Open

Establish naming convention for provider plugins #1

pmuens opened this issue Nov 11, 2016 · 1 comment
Labels
enhancement

Comments

@pmuens
Copy link
Contributor

pmuens commented Nov 11, 2016

It would be great to have a kind of naming convention for provider plugins so that one knows what the npm package does / what the GitHub repo is.

Here are my proposals for this:

  • serverless-provider-google (my favorite as the provider name in Serverless is google as well)
  • serverless-provider-google-cloud-functions
@jthomas
Copy link

jthomas commented Dec 5, 2016

👍 on having the provider id match the repo id.

pmuens pushed a commit that referenced this issue Oct 30, 2018
@knitterb
Merge pull request #1 from erikerikson/master
d810912 
disable comma dangle for es6 compatibility
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jthomas @pmuens