Skip to content

feat(http): improve error message for nullish header #46059

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

Conversation

markostanimirovic
Copy link
Contributor

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Issue Number: #46048

What is the new behavior?

Improved error message for nullish headers.

Does this PR introduce a breaking change?

  • Yes
  • No

@pullapprove pullapprove bot requested a review from AndrewKushnir May 19, 2022 10:53
@markostanimirovic markostanimirovic force-pushed the feat/http/nullish-header-error-message branch from 0bee9b2 to bbc0bd0 Compare May 19, 2022 11:25
@alxhub alxhub added the area: common/http Issues related to HTTP and HTTP Client label May 25, 2022
@ngbot ngbot bot added this to the Backlog milestone May 25, 2022
@AndrewKushnir AndrewKushnir added action: review The PR is still awaiting reviews from at least one requested reviewer target: patch This PR is targeted for the next patch release labels Jun 9, 2022
@markostanimirovic markostanimirovic force-pushed the feat/http/nullish-header-error-message branch 2 times, most recently from 6a77b4b to 98fa657 Compare June 14, 2022 21:03
This commit improves the error message for nullish headers.

Fixes angular#46048
@markostanimirovic markostanimirovic force-pushed the feat/http/nullish-header-error-message branch from 98fa657 to c646140 Compare June 15, 2022 21:11
Copy link
Contributor

@AndrewKushnir AndrewKushnir left a comment

Choose a reason for hiding this comment

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

@markostanimirovic thanks for addressing the feedback. The change looks good 👍

I've also ran tests in Google's codebase (internal link) and they came back as "green".

@AndrewKushnir AndrewKushnir added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release and removed action: review The PR is still awaiting reviews from at least one requested reviewer target: patch This PR is targeted for the next patch release labels Jun 16, 2022
@AndrewKushnir
Copy link
Contributor

This PR was merged into the repository by commit 82acbf9.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jul 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: common/http Issues related to HTTP and HTTP Client target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants