Improve the way nested types are rendered

Open
#40 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
api, documentation

Research direction

No source files or tests are named. Start with the public API documentation example for NumberField and trace the renderer that produces the FieldConfig_Number type; done means nested types expose their usable fields, omitted fields are removed, and the rendered type is navigable.

Written by the indexing model from the issue text.

Description

documentation

Example: https://developers.reddit.com/docs/api/public-api/#numberfield
FieldConfig_Number is not clickable, and there's no way for developer to know what fields they can use
If we unwrapped the FieldConfig_Number type and removed ommited ones, it would be easier to see what's possible

Dominant language
TypeScript
Stars
210
Forks
88
PR merge metrics
No merged PRs in 30d

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 reddit/devvit

All issues in reddit/devvit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.