aiken

Go to file

KtorZ 7883aff5f7 revert `619b73d03e` There's really no scenario where we want to generate boilerplate that always end up being removed. In particular, the boilerplate breaks tutorial as it generate conflicting validators in the blueprint. The only argument in favor of the boilerplate is to serve as example and show people some syntax reminder. However, this is better done in the README or on the user manual directly.		2023-08-22 12:59:36 +02:00
.github	test(ci): run examples too	2023-08-16 13:33:54 -04:00
aikup	Bump versions to 1.0.0-alpha, update CHANGELOG.	2023-04-13 17:35:21 +02:00
crates	revert `619b73d03e`	2023-08-22 12:59:36 +02:00
examples	test: fix acceptance tests	2023-08-16 14:52:06 -04:00
.editorconfig	rename examples/tests/{a,b,c,d,e,f} into examples/acceptance_tests/00{1,2,3,4,5,6}	2022-12-14 09:45:24 +01:00
.gitattributes	Add support for Nix flakes.	2023-02-07 13:16:17 +01:00
.gitignore	chore: re-add nix stuff from @waalge	2023-06-07 17:16:56 -04:00
CHANGELOG.md	revert `619b73d03e`	2023-08-22 12:59:36 +02:00
CONTRIBUTING.md	Update CONTRIBUTING.md	2023-07-04 08:33:15 -04:00
Cargo.lock	chore: Release	2023-08-19 20:17:00 -04:00
Cargo.toml	feat: finish splitting up parsers	2023-07-04 17:19:28 -04:00
LICENSE	chore: adjustment cargo.toml	2023-05-23 10:40:26 -04:00
README.md	chore: add stats to readme	2023-07-18 19:28:07 -04:00
flake.lock	chore: update flake	2023-07-27 10:23:10 -04:00
flake.nix	chore[nix]: remove unused cargoBuildFlags	2023-07-27 10:23:10 -04:00