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.

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

Propagation of response.encoding #79

Merged
merged 2 commits into from
Mar 6, 2021

Conversation

miro-balaz
Copy link
Contributor

As per http://www.softwareishard.com/blog/har-12-spec/#content , there is "encoding" field in content. I need to be able to use it, because in my project I am base64 encoding certain reponses.

@soulgalore
Copy link
Member

Hi @miro-balaz aha cool. I think you can fix the format issues with npm run lint:fix.

@miro-balaz
Copy link
Contributor Author

I think it should be ok now, i just commited it into my branch and it automatically appeared in PR, i didn't expect that.

@@ -79,8 +79,9 @@ module.exports = function(entry, response, page, options) {
status: response.status,
statusText: response.statusText,
content: {
encodig: response.encoding,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would be really useful to have!
May I suggest to have the property corrected to encoding?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See beatchristen@20b078e for my variant, which also tries to adhere to the 'optionality' aspect of the property.

@soulgalore
Copy link
Member

Oopss, I totally missed this PR, I'll merge and change the field name.

@soulgalore soulgalore merged commit 64111c5 into sitespeedio:main Mar 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants