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

chore(points): use points config from redux rather than Statsig #5232

Merged
merged 43 commits into from
Apr 17, 2024

Conversation

kathaypacific
Copy link
Collaborator

Description

This PR:

  • remove the statsig dynamic config
  • use the redux selectors to provide config to existing UI components
  • update unit tests (some were removed because the scenarios are tested in the saga and selector)

Test plan

n/a

Related issues

Backwards compatibility

Y

Network scalability

Y

</ScrollView>
<BottomSheet
snapPoints={['50%']}
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

this is a personal preference but the vertical spaces triggered me, particularly between the bottom of the button and the bottom of the screen. i think it's better to let the bottom sheet size itself (if we need to increase the height, we should add space above the button)

Copy link

codecov bot commented Apr 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.89%. Comparing base (7611678) to head (6254384).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #5232   +/-   ##
=======================================
  Coverage   85.89%   85.89%           
=======================================
  Files         745      745           
  Lines       30434    30473   +39     
  Branches     5276     5282    +6     
=======================================
+ Hits        26142    26176   +34     
- Misses       4055     4061    +6     
+ Partials      237      236    -1     
Files Coverage Δ
src/points/ActivityCardSection.tsx 95.45% <100.00%> (+5.45%) ⬆️
src/points/PointsHome.tsx 100.00% <100.00%> (ø)
src/statsig/constants.ts 100.00% <ø> (ø)
src/statsig/types.ts 100.00% <ø> (ø)

... 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 f696056...6254384. Read the comment docs.

const pointsConfig = getDynamicConfigParams(DynamicConfigs[StatsigDynamicConfigs.POINTS_CONFIG])

function makeSection(pointsMetadata: PointsMetadata): React.ReactNode {
function makeSection(pointsMetadata: PointsMetadata, sectionNumber: number): React.ReactNode {
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: is that an index? wdyt about naming it sectionIndex?

Base automatically changed from kathy/points-config-redux to main April 17, 2024 12:06
@kathaypacific kathaypacific added this pull request to the merge queue Apr 17, 2024
@kathaypacific kathaypacific removed this pull request from the merge queue due to a manual request Apr 17, 2024
@kathaypacific kathaypacific merged commit 67e2f6c into main Apr 17, 2024
16 checks passed
@kathaypacific kathaypacific deleted the kathy/points-config-switch branch April 17, 2024 13:12
shottah pushed a commit to zed-io/kolektivo that referenced this pull request May 15, 2024
…ra-inc#5232)

### Description

This PR:
- remove the statsig dynamic config
- use the redux selectors to provide config to existing UI components
- update unit tests (some were removed because the scenarios are tested
in the saga and selector)

### Test plan

n/a

### Related issues

- Related to RET-1044

### Backwards compatibility

Y

### Network scalability

Y

---------

Co-authored-by: Joseph Bergeron <jophish126@gmail.com>
Co-authored-by: Joe Bergeron <jbergero@alum.mit.edu>
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.

None yet

3 participants