deb-sig / deb-sig/double-entry-generator

Warning output when backend don't support the provider

Open
#170 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
719
Forks
102
PR merge metrics
No merged PRs in 30d

Description

> > Since this provider only support beancount output, what happened if I run this?
> > ```shell
> > double-entry-generator translate \
> > --config ./example/hxsec/config.yaml \
> > --provider hxsec \
> > --target ledger \
> > --output ./example/hxsec/example-hxsec-output.beancount \
> > ./example/hxsec/example-hxsec-records.xls
> > ```
>
> @Triple-Z Will generate a wrong ledger output without any warnings.

I think this PR can be merged, and we should grab a new issue about this for better user experience.

_Originally posted by @Triple-Z in https://github.com/deb-sig/double-entry-generator/issues/154#issuecomment-2983160171_

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by running the documented double-entry-generator translate command with the example/hxsec/config.yaml configuration, --provider hxsec, and --target ledger. Trace how provider and target support are checked, then verify that an unsupported combination produces a warning instead of silently generating a misleading Ledger output.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.