feat(import): add Splitwise API import for full expense history#660
Closed
Mufaddal5253110 wants to merge 1 commit into
Closed
feat(import): add Splitwise API import for full expense history#660Mufaddal5253110 wants to merge 1 commit into
Mufaddal5253110 wants to merge 1 commit into
Conversation
Collaborator
|
Sorry, I don't accept 100% vibe coded PRs and this is clearly one of them. Most importantly I cannot accept it due to the fact that it violates the Splitwise API ToS. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds direct Splitwise API import for complete expense history with individual transactions.
What it does:
paid_share/owed_sharecalculationscreatedAttimestamps for proper Activity orderingtransactionIdto prevent duplicates (safe to re-run)Files added:
src/lib/splitwise-api.ts- API client with paginationsrc/lib/splitwise-converter.ts- Conversion logicsrc/server/api/routers/splitwiseApiImport.ts- tRPC endpointssrc/pages/import-splitwise-api.tsx- UI for API key entry and group selectionsrc/tests/splitwise-converter.test.ts- 29 test casesCloses #307
Related to #465 (different approach - direct API vs external tool)
As noted in #307, Splitwise's API ToS prohibits use for competing services. This PR uses the direct API because the JSON export from export-splitwise only contains net balances, not individual expenses.
Options to discuss:
Demo
Checklist
CONTRIBUTING.mdin its entirety