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

adds statusCode projection #31

Merged
merged 2 commits into from
Mar 14, 2024
Merged

adds statusCode projection #31

merged 2 commits into from
Mar 14, 2024

Conversation

ValJed
Copy link
Contributor

@ValJed ValJed commented Mar 13, 2024

PRO-5716

Summary

Fix the fact that 301 redirects where 302. statusCode were undefined so 302 by default.

What are the specific steps to test this change?

Selecting 301 redirects actually should redirect with 301 status and not 302.

What kind of change does this PR introduce?

  • Bug fix
  • New feature
  • Refactor
  • Documentation
  • Build-related changes
  • Other

Make sure the PR fulfills these requirements:

  • It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
  • The changelog is updated
  • Related documentation has been updated
  • Related tests have been updated

Copy link

linear bot commented Mar 13, 2024

@ValJed ValJed requested a review from boutell March 13, 2024 14:24
@ValJed ValJed force-pushed the pro-5716-302-instead-of-301 branch from 0ca2527 to 0fba45b Compare March 13, 2024 14:24
@boutell
Copy link
Member

boutell commented Mar 13, 2024

Looks good be sure to add to the next release notes page

@ValJed ValJed merged commit 43d1a51 into main Mar 14, 2024
6 checks passed
@ValJed ValJed deleted the pro-5716-302-instead-of-301 branch March 14, 2024 09:58
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.

2 participants