Skip to content

refactor: Return headers in RESTController requests #2033

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

Merged
merged 1 commit into from
Oct 3, 2023

Conversation

dplewis
Copy link
Member

@dplewis dplewis commented Sep 28, 2023

Pull Request

Issue

See discussion: parse-community/parse-server#8766

Tasks

  • Add tests
  • Add changes to documentation (guides, repository pages, code comments)

@parse-github-assistant
Copy link

Thanks for opening this pull request!

  • ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

@codecov
Copy link

codecov bot commented Sep 28, 2023

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (64e6653) 100.00% compared to head (7dfac8b) 100.00%.
Report is 1 commits behind head on alpha.

❗ Current head 7dfac8b differs from pull request most recent head 90981d3. Consider uploading reports for the commit 90981d3 to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##             alpha     #2033   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           61        61           
  Lines         6168      6176    +8     
  Branches      1498      1496    -2     
=========================================
+ Hits          6168      6176    +8     
Files Coverage Δ
src/Cloud.js 100.00% <100.00%> (ø)
src/ParseObject.js 100.00% <100.00%> (ø)
src/Push.js 100.00% <100.00%> (ø)
src/RESTController.js 100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@dplewis dplewis requested a review from mtrezza September 28, 2023 14:44
Copy link
Member

@mtrezza mtrezza left a comment

Choose a reason for hiding this comment

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

Looks good; is this ready for merge?

@dplewis
Copy link
Member Author

dplewis commented Oct 3, 2023

This is ready to merge

@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.3.0-alpha.2

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Oct 3, 2023
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.3.1-beta.1

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Nov 16, 2023
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.3.1

@parseplatformorg parseplatformorg added the state:released Released as stable version label Nov 18, 2023
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.3.1-alpha.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released Released as stable version state:released-alpha Released as alpha version state:released-beta Released as beta version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants