lpil / lpil/json-typedef

Thoughts on a more `squirrel`-like usage pattern?

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

Nobody has claimed this yet.

Dominant language
Gleam
Stars
50
Forks
10
PR merge metrics
No merged PRs in 30d

Description

I reckon it could be nice to run this library like `gleam run -m json-typedef` to find JSON schemas in your `src/` directory and automatically write them out into a merged `.gleam` file.

Then you could get JSON syntax highlighting, not needing to worry of about string-escaping, and having a rapid and standardized way to regenerate the code when / if the schema changes?

Let me know what you think!

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.

Research direction

Start by reviewing the current json-typedef usage and the proposed `gleam run -m json-typedef` entry point. Define how schemas in `src/` are discovered, how JSON syntax is preserved, and what merged `.gleam` output and regeneration behavior would count as done.

Written by the indexing model from the issue text.

Assessment

Domain
cli, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.