Document Ledger payment gateways and GNU Taler#84
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
This PR updates the official Fleetbase Ledger documentation to make Payment Gateways a dedicated section under Payments and documents GNU Taler as a supported Ledger gateway.
What Changed
payments/gateways.mdxpage with a nested Payment Gateways section.Why
GNU Taler is now part of the Ledger gateway lifecycle and should be documented in the official Fleetbase docs rather than package-local markdown files. The docs now present all supported Ledger payment gateways in one discoverable section.
Validation
git diff --checkpassed.pnpm generate:api-docspassed when run with the arm64 Node runtime matching the installed esbuild binary.pnpm lintran but failed on pre-existing repo-wide TS/React lint issues unrelated to these docs changes.pnpm buildcompiled successfully, then failed during page data collection because the Ghost Content API returned HTTP 402 for/blog/[slug].Notes
Unrelated local changes in
vendor/postmanandpnpm-workspace.yamlwere intentionally left out of this PR.