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: internal refactor of loader to be structured like new mutation methods #254

Conversation

wschurman
Copy link
Member

@wschurman wschurman commented Feb 19, 2025

Why

After implementing #253 I noticed that the new pattern of the enforcing/withAuthorizationResult layer was quite a bit simpler the way I did it for the mutators than the way it was done for the loader.

This PR updates the loader to use the same pattern, where it is purely a concept for the entity class (user API) rather than used by any of the backing utilities/mutators/etc. Those all operate on the result loader and use enforce methods when needed.

How

Refactor internals. Note that this doesn't change the external API for loading.

Test Plan

This has full test coverage.

Copy link

codecov bot commented Feb 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (4d56065) to head (02c5ac3).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #254   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           78        78           
  Lines         2033      2029    -4     
  Branches       278       278           
=========================================
- Hits          2033      2029    -4     
Flag Coverage Δ
integration 100.00% <100.00%> (ø)
unittest 100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@wschurman wschurman force-pushed the @wschurman/02-19-chore_internal_refactor_of_loader_to_be_structured_like_new_mutation_methods branch 2 times, most recently from e7e4cc7 to adc8658 Compare February 20, 2025 00:04
@wschurman wschurman marked this pull request as ready for review February 20, 2025 00:52
@wschurman wschurman requested review from ide and quinlanj February 20, 2025 00:52
Copy link
Member Author

wschurman commented Feb 24, 2025

Merge activity

  • Feb 23, 10:20 PM EST: A user started a stack merge that includes this pull request via Graphite.
  • Feb 23, 10:24 PM EST: Graphite rebased this pull request as part of a merge.
  • Feb 23, 10:26 PM EST: A user merged this pull request with Graphite.

@wschurman wschurman changed the base branch from @wschurman/02-19-feat_make_load/create/update/delete_entity_authorization_result_interfaces_consistent to graphite-base/254 February 24, 2025 03:21
@wschurman wschurman changed the base branch from graphite-base/254 to main February 24, 2025 03:23
@wschurman wschurman force-pushed the @wschurman/02-19-chore_internal_refactor_of_loader_to_be_structured_like_new_mutation_methods branch from adc8658 to 02c5ac3 Compare February 24, 2025 03:24
@wschurman wschurman merged commit 92bac05 into main Feb 24, 2025
2 checks passed
@wschurman wschurman deleted the @wschurman/02-19-chore_internal_refactor_of_loader_to_be_structured_like_new_mutation_methods branch February 24, 2025 03:26
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