(327) Fix - Custom headers of one component can appear to another. #328
Conversation
This file contains 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
The problem was introduced with opencomponents#326 - In get-component.js the declaration of responseHeaders variable happens in a more global scope than it should be. For this reason every invocation of renderer function sees the changes in the headers made by previously requested components. The fix is to just move the declaration one scope inner. - Added a unit test to validate the fix - it tries to load two components subsequently. The first one does provide custom headers while the second one - don't. Then we check and expect to see there are no custom headers in the result for the second one.
|
Excellent, thanks @ivan-dimitrov-skyscanner |
|
This fixed #327 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The problem was introduced with #326 -
In get-component.js the declaration of responseHeaders variable happens in a more
global scope than it should be. For this reason every invocation of renderer
function sees the changes in the headers made by previously requested
components.
The fix is to just move the declaration one scope inner.
sequentially. The first one does provide custom headers while the second
one - doesn't. Then we check and expect to see no custom headers
in the result for the second one.