git.ipfire.org Git - thirdparty/FORT-validator.git/commit

]> git.ipfire.org Git - thirdparty/FORT-validator.git/commit

projects / thirdparty / FORT-validator.git / commit

author	Alberto Leiva Popper <ydahhrk@gmail.com>
	Wed, 29 Nov 2023 23:13:22 +0000 (17:13 -0600)
committer	Alberto Leiva Popper <ydahhrk@gmail.com>
	Wed, 29 Nov 2023 23:13:22 +0000 (17:13 -0600)
commit	63e71946db91119417b94bd09ea6829d8f11f84a
tree	94395d44f9f193be55b4c387ff6cd70d0ed52f74	tree
parent	f44a2ba335b933c46691824b06bd1378773da6fc	commit \| diff

Allow some nulls in the configuration JSON

While playing with the configuration sample, I found out that setting
a `null` slurm property in the JSON was rejected, even though the SLURM
file itself is not mandatory.

So rethink this, and for a few other fields as well.

src/config.c		diff \| blob \| blame \| history
src/config/str.c		diff \| blob \| blame \| history
src/config/types.h		diff \| blob \| blame \| history

Mirror of https://github.com/NICMx/FORT-validator.git

RSS Atom