Feature/refund eligibility helper - #145
Conversation
|
Someone is attempting to deploy a commit to the karagoz's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@laxjovial Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
Thanks for the refund eligibility helper work. I checked the latest commit, but this is not mergeable yet. Commands run: Blocking failures:
|
|
done , that . let me know if any other issues. also, im on the other issues |
|
I checked the current PR state before reviewing code, and GitHub still reports this branch as Please rebase or merge latest |
|
done please review |
|
Thanks for rebasing the refund eligibility helper PR. I rechecked this under the karagozemin account, but the PR is blocked before SDK tests because whitespace validation fails: Please strip trailing whitespace across the SDK files, then rerun:
After diff check is clean I can continue the functional review. |
|
i have reviewed and worked , better now? |
|
Thanks for the update. I rechecked the merge ref from the maintainer account and the SDK checks are green: git diff --check master...pr-145-merge
pnpm --filter @oversync/sdk test
pnpm --filter @oversync/sdk buildResult: SDK tests pass (75) and SDK build passes. I still cannot merge this exact PR because the diff is not scoped to #72. It includes refund eligibility, but also adds the explorer URL helper files/tests from #73 and SDK error normalization files/tests from #78: Those already have separate open PRs (#143 and #142). Please narrow this branch to the refund eligibility helper/tests only, or explicitly consolidate/close the other two PRs and link all affected issues in one PR. Once the scope is clean, the functional checks look ready. |
|
All three of my PR branches are now cleanly scoped to their respective issues. |
|
Thanks for the contribution! ✅ Logic looks fine, but |
c458b2d to
ff79cac
Compare
afa4ce8 to
ff79cac
Compare
|
done @karagozemin |
0c68542 to
6c54cf3
Compare
|
@karagozemin come and see |
|
Rechecked: thanks for the updates. However this PR now has merge conflicts with |
|
Done |
closes #72