visgl / visgl/deck.gl-community

Tracker: @deck.gl/json v2

Open
#596 6 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
101
Forks
60
Avg merge
1d 12h
Merged PRs (30d)
41

Description

Target Use Case
  • Enable LLMs to generate deck.gl visualizations.
  • Enable JSON schemas for editors like Monaco
  • Add zod definitions to validate deck.gl JSON.
  • Strengthen pydeck capabilities
  • Better playground application
  • ...
Proposal

Create a new module in deck.gl-community where we iterate and build a clean solution that we then propose for upstreaming into deck.gl/json

Details
  • Move the expression parser in deck.gl to @math.gl/expressions
  • Implement a catalog of Zod schemas for deck layer props, views etc.
  • Generate JSON schemas for deck.gl JSON from the Zod schemas and publish/export them.
  • Build out a playground v2 example in community repo that leverages all the features.
  • Make the JSON LLM friendly, examples docs LLM.txt etc so that LLMs can easily generated correct deck.gl JSON.
  • Provide a way to hook data sources into deck.gl/json, especially SQL sources (e.g. see the new SQLSourceLoader in upcoming loaders.gl v5.0 release)
  • ...

Contributor guide

Open the contributing guide

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

This is a broad tracker with no files or tests named. Start by reviewing the existing deck.gl expression parser and the proposed SQLSourceLoader reference, then break the checklist into separately scoped tasks. Done requires an agreed community module plan covering schemas, generated JSON schemas, the playground, documentation, and data-source integration.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
data-visualization, documentation, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.