Skip to content
This repository was archived by the owner on Dec 5, 2022. It is now read-only.

Conversation

@atkinchris
Copy link

@atkinchris atkinchris commented May 8, 2020

This corrects the type definition for requestFragment, which does not match it's implementation. This resolves #327 and closes #297.

This also corrects initialisation of custom requestFragment functions, which otherwise are not invoked to close over filterHeaders.

This also corrects the type definition for parseTemplate and resolves #329.

atkinchris added 3 commits May 8, 2020 22:30
This corrects the type definition for requestFragment, which does not match it's implementation. This resolves zalando#327 and supercedes https://github.com/zalando/tailor/pull/297/files.

This also correct initialisation of custom `requestFragment` functions, which otherwise are not invoked to close over `filterHeaders`.
@atkinchris atkinchris changed the title Correct requestFragment type and initialisation Correct parseTemplate type, and requestFragment type and initialisation May 9, 2020
@atkinchris
Copy link
Author

The tests are failing on Node 12, but not on earlier versions (on Travis and local). Is this related to #322?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

parseTemplate type definition does not match implementation requestFragment type definition does not match implementation

1 participant