quickstart VS tabnine-vscode

I was able to get the Plaid API working with n8n an hour or go. I am going to build off of it to create exactly what I need. I used https://github.com/plaid/quickstart to spin up a sample app, login, link my account and get my access token. Then I can take that access token and include it in a HTTP post request to the Plaid API's get transactions endpoint. I can select transactions from a certain date range (today) as well as account balances and run it on a cron job once per day. Each transaction has a transactionId which will help me avoid duplicates. I can then push this info into Google Sheets, Notion, a database or wherever. If I use Google Sheets I can add graphs or link it to Google Data Studio and build a dashboard showing exactly what I need. Yes, it is more steps than using some existing application but the flexibility to create exactly what I need is worth it for me. I am not far enough yet to say if there will be any hiccups or not, but so far it is looking like clear skies ahead.

Also, looks like this might help: https://github.com/plaid/quickstart

git clone https://github.com/plaid/quickstart.git cd quickstart/python # Copy the .env.example file to .env, then fill # out PLAID_CLIENT_ID and PLAID_SECRET in .env cp .env.example .env # Install dependencies pip install -r requirements.txt # Start the backend app ./start.sh

Both are related to limitations of vscode completion engine, so Tabnine can't really blamed for them in any way.

1. Initially Tabnine's auto-completion was triggered on any character, which best leveraged Tabnine's power but also had inherent problem: when Tabnine was triggered on non-letter character it sometimes prevented Vscode from showing suggestions from other completion sources (LSPs, snippets). There is a discussion in https://github.com/codota/tabnine-vscode/issues/6 with me explaining that the only viable solution is to reduce set of trigger characters to letters only. In the end a fix was pushed that reduced the set of trigger characters, which made the problem less likely but still not solved. The are numerous duplicates of this issue on Github.

2. Another problem is when Vscode has auto-completion suggestions from Tabnine and other sources (LSP, snippets), it frequently puts Tabnine's at the top of list. This is a big no-go for me because most of the time just want to complete the identifier (class field, method etc.). Modifying just the extension code didn't help so in the end I had add a small patch to Vscode itself, which gives lowest score to Tabnine's candidates: https://github.com/sergei-dyshel/vscode/commit/ee73034b9ec6c....

I must admit that both problems can be practically solved by new "inline auto-completion" mechanism in vscode which looks very promising for AI-based completion in general. I'm looking forward to evaluate it.