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

fix(client): key order #318

Merged
merged 3 commits into from
Sep 22, 2023
Merged

fix(client): key order #318

merged 3 commits into from
Sep 22, 2023

Conversation

DenizYil
Copy link
Contributor

Closes #314 as discussed in #317.

@codecov
Copy link

codecov bot commented Sep 21, 2023

Codecov Report

Merging #318 (0df0977) into main (71f2c2a) will not change coverage.
The diff coverage is n/a.

❗ Current head 0df0977 differs from pull request most recent head e1893c1. Consider uploading reports for the commit e1893c1 to get more accurate results

@@           Coverage Diff           @@
##             main     #318   +/-   ##
=======================================
  Coverage   98.11%   98.11%           
=======================================
  Files          52       52           
  Lines        2335     2335           
  Branches      327      286   -41     
=======================================
  Hits         2291     2291           
  Misses         29       29           
  Partials       15       15           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@dionhaefner
Copy link
Collaborator

Awesome, thanks!

@dionhaefner dionhaefner merged commit 329d885 into main Sep 22, 2023
@dionhaefner dionhaefner deleted the fix/client-key-order branch September 22, 2023 12:54
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.

terracotta connect requesting metadata keys in wrong order
2 participants