Quick whip through to try and standardis(z)e some language, looks like
the most common English in the docs is US English so I chose that one,
but if we'd prefer the Queen's then that's okay too.
---------
Co-authored-by: Ruben Olsen Lærk <ruben@lku.no>
This adds missing documentation for existing API calls and removes one
that does not exist.
---------
Co-authored-by: Matiss Janis Aboltins <matiss@mja.lv>
Removed api methods that do not exist. Since they don't exist - they
should not be in the docs.
It would be nice to implement them though.. but until they are
implemented - lets not mislead people.
Added clarity about migrating from YNAB or Mint to Actual.
Corrected grammatical error about what Actual officially supports for
importing from other budgeting apps.
Related to https://github.com/actualbudget/actual/issues/1695
It's pretty common for users to have self-signed certificates for
actual, but this presents some challenges for the API.
Give a little bit of guidance here, for new contributors. Really, all
the info here is just for Node.js and not for actual. (we would want to
create seperate http agents and our own certificate config system if we
wanted to have actual specific config for this).
For many of the existing api use-cases the
`NODE_TLS_REJECT_UNAUTHORIZED` option will be fine. But
`NODE_EXTRA_CA_CERTS` seems like the proper way to do things (and the
one I tested on nodejs 21, on ubuntu via asdf install). But I also made
sure to mention the option of using openssl's ca certificates, because
if you are in a situation where your node.js is configured to link to
the system openssl on Linux, it's going to be the easiest and most
familiar to Linux sysadmins. It's just not the cross-platform supported
option like `NODE_EXTRA_CA_CERTS`.
So they point to existing implementations. The current links are broken
and Im hoping these links are correct - someone please let me know if
this is incorrect, thanks
