Feature/optionaltsheaders #4560
Open
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
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.
Adding option for including optional headers in generated TypeScript client code.
Purpose is to allow clients to add any additional headers one might need, without having to change the backend.
Different logging providors like Appliction Insights, log what headers are sent, which can be used for debugging purposes.
This also detaches backend and frontend, with a freedom to exercise a development process, without having to depend on backend changes.
Help: Please help verify liquid templates, in order to verify the comma is set properly, for multiple combinations. I've tried my best.
Disclaimer: First PR, so be gentle 😇