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(points): prevent sagas spawning if points are disabled #5385

Merged
merged 2 commits into from
May 6, 2024

Conversation

kathaypacific
Copy link
Collaborator

@kathaypacific kathaypacific commented May 3, 2024

Description

As the title. Rather than remembering to check the remote config in each saga, catch it all at the root level. We should not start talking to the points DB yet.

Test plan

n/a

Related issues

n/a

Backwards compatibility

Y

Network scalability

If a new NetworkId and/or Network are added in the future, the changes in this PR will:

  • Continue to work without code changes, OR trigger a compilation error (guaranteeing we find it when a new network is added)

Copy link

codecov bot commented May 3, 2024

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 86.07%. Comparing base (9aae469) to head (40b50c5).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #5385      +/-   ##
==========================================
- Coverage   86.09%   86.07%   -0.02%     
==========================================
  Files         737      737              
  Lines       30016    30016              
  Branches     5143     5143              
==========================================
- Hits        25841    25837       -4     
- Misses       3948     3951       +3     
- Partials      227      228       +1     
Files Coverage Δ
src/points/saga.ts 84.90% <0.00%> (-3.78%) ⬇️

... and 1 file with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9aae469...40b50c5. Read the comment docs.

Copy link
Contributor

@bakoushin bakoushin left a comment

Choose a reason for hiding this comment

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

@kathaypacific kathaypacific merged commit 7eb6fd7 into main May 6, 2024
15 of 16 checks passed
@kathaypacific kathaypacific deleted the kathy/fix-points-calls branch May 6, 2024 12:20
shottah pushed a commit to zed-io/kolektivo that referenced this pull request May 15, 2024
…c#5385)

### Description

As the title. Rather than remembering to check the remote config in each
saga, catch it all at the root level. We should not start talking to the
points DB yet.

### Test plan

n/a

### Related issues

n/a

### Backwards compatibility

Y

### Network scalability

If a new NetworkId and/or Network are added in the future, the changes
in this PR will:

- [x] Continue to work without code changes, OR trigger a compilation
error (guaranteeing we find it when a new network is added)
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