This repository was archived by the owner on Jan 29, 2022. It is now read-only.
Fix a parser issue with the module endpoint#137
Merged
dhollinger merged 1 commit intovoxpupuli:masterfrom Jul 21, 2020
Merged
Conversation
bastelfreak
approved these changes
Jul 21, 2020
Member
bastelfreak
left a comment
bastelfreak
left a comment
There was a problem hiding this comment.
verified this locally. The patch fixes my error from #136
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was an issue in the code where the Headers were not getting sent to the parser on the module endpoint causing the parser to error out as it was missing an argument. Since both the environment and module endpoints need this data, I moved the
req_bodyandheadersmethods in toApplicationController