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

Invoke throws 400 error when using -p option #320

Closed
tbarlow12 opened this issue Sep 9, 2019 · 0 comments
Closed

Invoke throws 400 error when using -p option #320

tbarlow12 opened this issue Sep 9, 2019 · 0 comments
Labels
pr-pending Issues that have a pending PR associated with them

Comments

@tbarlow12
Copy link
Collaborator

Invoke works fine when using -d and passing the stringified JSON, but fails when using a path to sample data
@tbarlow12 tbarlow12 mentioned this issue Sep 9, 2019
Merged
@tbarlow12 tbarlow12 added the pr-pending Issues that have a pending PR associated with them label Sep 9, 2019
tbarlow12 added a commit that referenced this issue Sep 10, 2019
@tbarlow12
fix: Fix failing invoke with data path (#321)
7adf5d6 
Moves data path initialization outside of the constructor and does not replace the `data` property within options. Instead, passes the contents of the file path to the invoke service.

Fixes #320
tbarlow12 added a commit that referenced this issue Sep 13, 2019
@tbarlow12
fix: Fix failing invoke with data path (#321)
bad7146 
Moves data path initialization outside of the constructor and does not replace the `data` property within options. Instead, passes the contents of the file path to the invoke service.

Fixes #320
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pr-pending Issues that have a pending PR associated with them
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tbarlow12