Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

More verbose assertion

Open
#848 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
compilers

Research direction

Start at typify-impl/src/convert.rs around line 395 and inspect the assertion that produces the reported message. Trace which schema information is available there; done means the assertion reports a human-readable message that identifies the relevant part of the schema.

Written by the indexing model from the issue text.

Description

This assertion triggers for me:
https://github.com/oxidecomputer/typify/blob/1f9bc52283ad7b449db2db77efc5d8e922ec7f4d/typify-impl/src/convert.rs#L395

... and I have no idea what that means, nor which part of the schema it is about.
Could it be made more humanly-digestable somehow?

Dominant language
Rust
Stars
898
Forks
114
Avg merge
4h 18m
Merged PRs (30d)
14

Contributor guide

No contributing guide indexed for this repository

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 oxidecomputer/typify

All issues in oxidecomputer/typify

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.