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

prefix parameter not supported #562

Closed
dnp1 opened this issue May 19, 2022 · 3 comments · Fixed by #564
Closed

prefix parameter not supported #562

dnp1 opened this issue May 19, 2022 · 3 comments · Fixed by #564
Labels

Comments

@dnp1
Copy link

dnp1 commented May 19, 2022

No description provided.

@NoxHarmonium
Copy link
Collaborator

Hi @dnp1, would you be able to provide me with some more information about your issue? Which prefix parameter are you referring to?

@NoxHarmonium
Copy link
Collaborator

Oh I think I've found what you mean, prefix isn't part of the config schema so you can't specify it at the moment, even though it is mentioned in the codebase.

I found that out while working on #313 so when I get a PR up for that, it should also fix this issue.

NoxHarmonium added a commit that referenced this issue May 24, 2022
- Although not documented in the readme, there are code paths that allow prefix to be overridden via config. I'm unsure whether this was a feature that was only partially implemented, or maybe an existing feature that was broken at some point, so to be on the safe side, I'll add it to the config schema, but leave it undocumented for now.
NoxHarmonium added a commit that referenced this issue May 24, 2022
- runServerless is a tool that the serverless team use themselves to test the framework
- It allows us to make sure that the plugin in being tested with all the right lifecycle hooks. For example, runServerless will actually validate the provided config against the provided schema, which has already uncovered a bug (#562)
- One downside is that we now have build the code as part of running tests, as serverless needs to be able to import the plugin dynamically. However, it seems like this is an acceptable trade off at the moment because building is quite fast (faster than the tests themselves)
- Not all the tests run via runServerless yet, but as we go along we should update more tests where appropriate
NoxHarmonium added a commit that referenced this issue May 24, 2022
- runServerless is a tool that the serverless team use themselves to test the framework
- It allows us to make sure that the plugin in being tested with all the right lifecycle hooks. For example, runServerless will actually validate the provided config against the provided schema, which has already uncovered a bug (#562)
- One downside is that we now have build the code as part of running tests, as serverless needs to be able to import the plugin dynamically. However, it seems like this is an acceptable trade off at the moment because building is quite fast (faster than the tests themselves)
- Not all the tests run via runServerless yet, but as we go along we should update more tests where appropriate
NoxHarmonium pushed a commit that referenced this issue May 24, 2022
## [2.0.1](v2.0.0...v2.0.1) (2022-05-24)

### Bug Fixes

* add 'prefix' to config schema (fixes [#562](#562)) ([4602a63](4602a63))
@NoxHarmonium
Copy link
Collaborator

🎉 This issue has been resolved in version 2.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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 a pull request may close this issue.

2 participants