Idea: Use modules instead of YAML for evals

Open
#5 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
elixir
Domain
tooling

Research direction

Start by reviewing the existing YAML definitions and the assertion code referenced in the issue, then read the comment discussion for the unresolved design concerns. Done means there is an agreed approach for representing evals with Elixir modules and a helper, but the issue does not name files, tests, or more specific acceptance criteria.

Written by the indexing model from the issue text.

Description

enhancement
Is your feature request related to a problem? Please describe.

So, I don't really understand why you'd want YAML definitions for this, especially given the awkward assertion code.

Describe the solution you'd like

It would make more sense to me to use normal Elixir modules with perhaps a helper use. Like, why complicate things?

Describe alternatives you've considered

No response

Additional context

No response

Dominant language
Elixir
Stars
51
Forks
6
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ash-project/evals

All issues in ash-project/evals

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.