Novus Nota

> Got one idea just now: a sub-command `config`, which would deal with `tact.config.json`. Another sub-command options: 1. `tact fmt`, source code formatter #162 2. `tact doc`, for auto-generating docs...

Although it's just a rough idea, I think that compiler's CLI and/or API can be extended to allow switching between compiler versions or controlling available compiler versions per project. This...

Perhaps, it would be reasonable to keep the compiler's CLI and simply rename `bin/tact` into `bin/tactc` to avoid confusion with the upcoming general Tact CLI. Although I'm in full support...

Having `--boc` and `--boc64` flag for only outputting BoC in binary and Base64 formats may be a nice addition to the compilation `mode`s

> `Address` is supported since PR #175, will be released in v1.3.0 Which makes all native data types supported in `dump()` function. [Soon-to-be documented](https://github.com/tact-lang/tact-docs/pull/160)

Here's the cram fork we might use, which continues developing its snapshot-based testing approach: https://github.com/prysk/prysk

What if we only use it in CI? Although I agree with your point.

Jest has support for snapshot testing, which is probably the most compatible solution to our current repo layout: https://jestjs.io/docs/snapshot-testing Although we'll have to wrap CLI calls a bit (in `child_process`...

Initial prototype (using `awk` from GNU coreutils) was done by a community member @0kenx: https://github.com/microcosm-labs/tact-tools/tree/main/tactdoc. It's a nice first step! :fire:

Great page in Elixir docs on writing documentation, adding here for future reference in our docs and future pages, such as Effective Tact or something :) https://hexdocs.pm/elixir/writing-documentation.html