feat(frontend): Next.js scaffolding + core config model + YAML serializers - #76
Open
maan-iitd2 wants to merge 3 commits into
Open
feat(frontend): Next.js scaffolding + core config model + YAML serializers#76maan-iitd2 wants to merge 3 commits into
maan-iitd2 wants to merge 3 commits into
Conversation
…izers Foundation for InGen Studio, a Next.js 15 / React 19 SPA for building ingen YAML configs visually. This PR ships only the non-visual base that later UI PRs build on: - Build scaffolding: package.json/lock, next.config.mjs, jsconfig.json (@/* import alias), eslint.config.js, .env* (adapter-mode config: mock vs http), public/ assets. - src/models/: the in-memory config shape everything else depends on (configModel, types, constants) plus applyIntent/interfaceOps, the deterministic executor for the inChat assistant's ops. - src/serializers/: lossless YAML <-> model round-trip. - src/utils/id.js, src/lib/fuzzy.js: small, dependency-free helpers that models/applyIntent import directly (pulled forward from the later state/hooks/lib wave since configModel and applyIntent need them to even load). Routing, adapters/services, state, and all UI components are separate follow-up PRs — this PR alone does not build a running app (no src/app/ yet), by design. ## Testing - `npm run lint` — clean. - `npm run test` — 43/43 passed (models + serializers unit tests, including round-trip yaml -> model -> yaml losslessness). Signed-off-by: maan-iitd2 <maan.iitd.ac.in@gmail.com>
Jatin-8898
approved these changes
Aug 6, 2026
Comments cited a DESIGN.md that does not exist in this repository, and
internal project-phase vocabulary ('Phase 0/1/5.1') that is meaningless
to an external reader. Replace them with descriptions of what the code
actually does.
Signed-off-by: maan-iitd2 <maan.iitd.ac.in@gmail.com>
The filename referenced an internal project phase rather than the ops under test. Signed-off-by: maan-iitd2 <maan.iitd.ac.in@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
First frontend PR: InGen Studio, a Next.js 15 / React 19 SPA for building ingen YAML configs visually. This PR ships only the non-visual foundation:
package.json/lock,next.config.mjs,jsconfig.json(@/*→src/*alias),eslint.config.js,.env*(adapter-mode config —mock: localStorage + simulated runs, no backend needed;http: talks to the FastAPI wrapper in feat(backend): thin FastAPI wrapper around the ingen CLI #75),public/assets.src/models/— the in-memory config shape everything else depends on (configModel,types,constants), plusapplyIntent/interfaceOps, the deterministic executor that turns the inChat assistant's{ops}into model mutations.src/serializers/— lossless YAML ↔ model round-trip (yamlSerializer/yamlDeserializer).configModel/applyIntentimport them directly and won't load without them:src/utils/id.js(id generation) andsrc/lib/fuzzy.js(Levenshtein distance, used for inChat's "did you mean 'status'?" column-typo correction).Not in this PR, by design: routing (
src/app/), adapters/services, state/hooks, or any UI component. This PR alone does not build a running app — that lands over the next few PRs (adapters/state → app shell → editor UI), each building on this one.Testing
npm install && npm run lint— clean, no errors.npm run test— 43/43 passed, covering the config model (add/remove/rename/reorder interfaces and sources, validation),applyIntent(including a dedicated suite for the remove/add-transform ops), and the YAML serializers (round-trip losslessness, deterministic/idempotent output, key ordering, empty-section dropping).What it looks like
This PR is a library layer with no UI of its own, but the serializer is what produces the YAML a
user actually ships. Below is
modelToYamloutput rendered live in the Studio — key ordering,section ordering and empty-section dropping are all this PR's code:
🤖 Generated with Claude Code