Tripletex / Tripletex/tripletex-api2
Missing support for attachments or metadata
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 49
- Forks
- 47
- Avg merge
- 1h 1m
- Merged PRs (30d)
- 1
Description
While APIs like Fiken allow for attachments and Stripe allow for general metadata arrays Trippeltex does not allow for anything like this attached to invoices which makes it a big hassle to work with. Instead of letting your accounting system be a source of truth it will require extra handling of data outside of the system.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, or entry points; begin by reviewing the existing invoice API resources and examples, then compare the attachment and metadata capabilities referenced for Fiken and Stripe. The work is complete only when the required invoice attachment or metadata behavior, API surface, and acceptance criteria are defined and implemented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100