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

Create smaller package for just serverless file parsing #7966

Open
jadamon42 opened this issue Jul 21, 2020 · 1 comment
Open

Create smaller package for just serverless file parsing #7966

jadamon42 opened this issue Jul 21, 2020 · 1 comment
Assignees
Labels

Comments

@jadamon42
Copy link

Use case description

I am creating a plugin for VSCode. For this plugin in, I need to be able to reliably parse serverless files. When including serverless as a dependency, this becomes quite simple. However, this increases the size of my package by nearly 200x! All I need is a simple parser, not all the bells and whistles. People have tried to make parsers for serverless files, but they generally do not work well. For those in a situation similar to mine, a small serverless parsing package would be ideal.

Proposed solution

Release some sort of smaller package designed specifically for parsing serverless files. This way, people can create plugins, extensions, or whatever else using the serverless format and share them with the community.

@medikoo
Copy link
Contributor

medikoo commented Jul 22, 2020

@jadamon42 great thanks for that proposal. Still due to how Servelress Framework works, what you have in mind is not that doable. Thing is that parsing and resolving fully a serverless config involves many layers, as resolving variables, which may reference config parts from other files or external services, or supporting plugin resolvers (and that requires loading of all plugins of a service).

So even if that theoretically could be minimized a bit, it'll be probably just a fraction and not a significant slice as you may assume.

We're currently working on a schema based validation for config files, and we discussed exactly this matter there. See #6562 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants