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

feat(code_push_protocol): Add GetReleasePatchesResponse #1094

Merged
merged 1 commit into from
Aug 14, 2023

Conversation

bryanoltman
Copy link
Contributor

@bryanoltman bryanoltman commented Aug 14, 2023

Description

This will be used as a response type to /api/v1/apps/$appId/releases/$releaseId/patches, which will allow clients to list patches and their artifacts for a given release.

Part of #1095

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@codecov
Copy link

codecov bot commented Aug 14, 2023

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (29517a5) 100.00% compared to head (f6c7327) 100.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##              main     #1094    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files           87       165    +78     
  Lines         3328      4205   +877     
==========================================
+ Hits          3328      4205   +877     
Files Changed Coverage Δ
..._release_patches/get_release_patches_response.dart 100.00% <100.00%> (ø)
...elease_patches/get_release_patches_response.g.dart 100.00% <100.00%> (ø)

... and 76 files with indirect coverage changes

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

Json toJson() => _$GetReleasePatchesResponseToJson(this);

/// Patch numbers for a given release mapped to their artifacts.
final Map<int, List<PatchArtifact>> patches;
Copy link
Contributor

Choose a reason for hiding this comment

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

Does this need to be a Map? Couldn't this be a List<PatchArtifact> since the patchId is part of the artifact?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The artifact doesn't know which patch number (not ID) it's related to, and I think we probably want to display patch numbers on the client.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah yeah nvm I misread makes sense 👍

@bryanoltman bryanoltman requested a review from felangel August 14, 2023 16:47
@bryanoltman bryanoltman merged commit 95536e7 into main Aug 14, 2023
@bryanoltman bryanoltman deleted the bo/get-release-patches-response branch August 14, 2023 17:59
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