When a user provides an invalid toml config that fails to be parsed, air will silently continue with default settings. Very confusing if you are debugging what's going on.
Output from air with the above setup (simply typing air from dir with the .air.toml file):
$ air
__ _ ___
/ /\ | | | |_)
/_/--\ |_| |_| \_ v1.49.0, built with Go go1.21.6
watching .
watching app
watching cmd
watching cmd/urchin
watching common
watching database
watching migrations
watching static
watching templates
watching templates/contact
watching templates/index
watching templates/post
watching templates/services
!exclude tmp
building...
no Go files in /home/matheus/development/urchin
failed to build, error: exit status 1
Output when running air -c .air.toml - a correct output:
$ air -c .air.toml __ _ ___
/ /\ | | | |_)
/_/--\ |_| |_| \_ v1.49.0, built with Go go1.21.6
2024/01/22 21:59:42 (24, 3): The following key was defined twice: build.full_bin
When a user provides an invalid toml config that fails to be parsed,
air
will silently continue with default settings. Very confusing if you are debugging what's going on.Example of wrong
.air.toml
config:Note the multiple defined
full_bin
. For clarity, I was wondering why the followingMakefile
wasn't running properly:Output from air with the above setup (simply typing
air
from dir with the.air.toml
file):Output when running
air -c .air.toml
- a correct output: