Implement fuzzy search that does not rely on fzf #2

New Issue

felixm · 2023-10-16T20:55:49+02:00

felixm commented

2023-10-16 20:55:49 +02:00

When pressing enter, the best matching candidate should be completed.

Moving up and down the list should be supported. (Cycle through start index.)

When no match is found, the entered string should be accepted as account.

When pressing enter, the best matching candidate should be completed. Moving up and down the list should be supported. (Cycle through start index.) When no match is found, the entered string should be accepted as account.

felixm referenced this issue from a commit

2023-10-17 13:45:22 +02:00

Implement option to add account2s and commodities to resolve #2.

felixm closed this issue

2023-10-17 13:45:22 +02:00

felixm commented

2023-10-17 13:46:54 +02:00

In general, it would still be desirable to get rid of fzf.

However, this issue was more about addressing the issue that accounts could not be added.

With this commit, this is now possible by specifying accounts via the JSON file. This has the additional benefit that --strict can be used for additional verification of the data.

In general, it would still be desirable to get rid of fzf. However, this issue was more about addressing the issue that accounts could not be added. With this commit, this is now possible by specifying accounts via the JSON file. This has the additional benefit that `--strict` can be used for additional verification of the data.

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: felixm/ledgerai#2