Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement eval.nix output schema validation with yants #81

Open
blaggacao opened this issue May 1, 2022 · 0 comments
Open

Implement eval.nix output schema validation with yants #81

blaggacao opened this issue May 1, 2022 · 0 comments

Comments

@blaggacao
Copy link
Contributor

blaggacao commented May 1, 2022

Several tickets deal with more flexibility of the nix eval schema.

#73 prepares the ground to make eval.nix swappable.

Now, in order to ensure the required cli contracts are met at all times, we might consider typing the eval output contract with yants.

https://github.com/divnix/yants

I also think strengthening this contract/interface will help to increase it's maintainability over time.

@blaggacao blaggacao changed the title Implement the eval.nix output schema validation with yants Implement eval.nix output schema validation with yants May 1, 2022
blaggacao added a commit to blaggacao/colmena that referenced this issue May 1, 2022
- this is useful for custom evaluators which implement custom
  hive or flake schemata.

- as long as they satisfy the `hive` contract (currently a bit implicit)

closes: zhaofengli#81
blaggacao added a commit to blaggacao/colmena that referenced this issue May 26, 2022
- this is useful for custom evaluators which implement custom
  hive or flake schemata.

- as long as they satisfy the `hive` contract (currently a bit implicit)

closes: zhaofengli#81
blaggacao added a commit to blaggacao/colmena that referenced this issue May 26, 2022
- this is useful for custom evaluators which implement custom
  hive or flake schemata.

- as long as they satisfy the `hive` contract (currently a bit implicit)

closes: zhaofengli#81
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant