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

Setting paramsConfig to a default value of {} to indicate that it wasn't passed breaks configuration and causes Buster to crash. #12

Closed
jeffschwartz opened this issue Jan 5, 2019 · 0 comments
Closed

Setting paramsConfig to a default value of {} to indicate that it wasn't passed breaks configuration and causes Buster to crash. #12

jeffschwartz opened this issue Jan 5, 2019 · 0 comments
Assignees
@jeffschwartz
Labels
bug Something isn't working
Milestone
v0.2.3

Comments

@jeffschwartz
Copy link
Collaborator

jeffschwartz commented Jan 5, 2019 •
edited
Loading

Setting paramsConfig to {} breaks configuration and should be removed.
@jeffschwartz jeffschwartz added the bug Something isn't working label Jan 5, 2019
@jeffschwartz jeffschwartz added this to the v0.2.3 milestone Jan 5, 2019
@jeffschwartz jeffschwartz self-assigned this Jan 5, 2019
jeffschwartz added a commit that referenced this issue Jan 5, 2019
@jeffschwartz
no longer setting paramsConfig to default value - addresses issue #12
255c209
@jeffschwartz jeffschwartz changed the title setting paramsConfig to default value breaks configuration Setting paramsConfig to default value breaks configuration Jan 5, 2019
@jeffschwartz jeffschwartz changed the title Setting paramsConfig to default value breaks configuration Setting paramsConfig to default value to indicate that it wasn't passed breaks configuration Jan 5, 2019
@jeffschwartz jeffschwartz changed the title Setting paramsConfig to default value to indicate that it wasn't passed breaks configuration Setting paramsConfig to default value {} to indicate that it wasn't passed breaks configuration Jan 5, 2019
@jeffschwartz jeffschwartz changed the title Setting paramsConfig to default value {} to indicate that it wasn't passed breaks configuration Setting paramsConfig to a default value of {} to indicate that it wasn't passed breaks configuration Jan 5, 2019
@jeffschwartz jeffschwartz changed the title Setting paramsConfig to a default value of {} to indicate that it wasn't passed breaks configuration Setting paramsConfig to a default value of {} to indicate that it wasn't passed breaks configuration and causes Buster to crash. Jan 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeffschwartz jeffschwartz

Labels
bug Something isn't working
Projects
None yet
Milestone
v0.2.3
Development

No branches or pull requests
1 participant
@jeffschwartz