Closed nprzy closed 3 weeks ago
As far as I can recall, like much of this project, the current naming convention was just something I pulled out of my butt when I first wrote this, so I'm definitely open to changing it.
Making it configurable like the commit you linked is probably the best approach. That said, if we have reasonable confidence that the new configuration is better across the board, I don't mind making that the new default and reacting if users don't like it.
Might also be a good time to deprecate the useNameForDestination
config option if that makes sense.
Any objections to something like this? https://github.com/nprzy/firefly-plaid-connector-2/commit/e366145c1a2b3ec05e3086150e88d2d0f3b72430
Lets the user configure a SpEL expression to fully customize their description. I'm thinking about something similar for the notes field too.
No objections; looks like good stuff to me.
I noticed that the Firefly transaction titles are often a bit redundant. Here are a few examples from my own accounts:
The names are currently generated as
"${plaidTx.name}: ${plaidTx.originalDescription}"
.A few observations and thoughts:
name
field in favor ofmerchant_name
. At least in my own transaction data, I pretty universally prefer merchant_name over name. I would personally prefer not to havename
propagated into my FF transactions at all.I've started addressing this in my own fork (https://github.com/nprzy/firefly-plaid-connector-2/commit/8f08c284911aade9655fa927f6bd4cf8190dc7c1) but I'm not really happy enough with the solution yet to submit a PR. I figured I'd open an issue instead and see if anyone else had thoughts/preferences.