Skip to content

Conversation

@antoniocapelo
Copy link
Collaborator

@antoniocapelo antoniocapelo commented Jul 10, 2025

Overview

This PR moves the source code from next/ to the main project root, officially making v1 the primary version of @remoteoss/json-schema-form. The legacy v0 version has been moved to a dedicated v0/ subdirectory for maintenance.

Main Changes

Project Structure

  • Clean Root: Established v1 as the main development focus

New Migration Documentation

  • MIGRATING.md: Comprehensive 277-line migration guide covering:
    • Deprecated configs/output from v0 to v1
    • API changes and deprecations
    • Step-by-step migration instructions
    • Common issues and solutions
    • TypeScript improvements
    • ESM-only package structure

Project Configuration

  • Root-level Config: Moved all v1 configuration to project root
    • package.json, tsconfig.json, eslint.config.mjs
    • babel.config.mjs, jest.config.mjs
  • Git Submodules: Updated path from next/json-schema-test-suite to root level
  • ESLint: Added v0 and scripts to ignore patterns

Documentation Updates

  • README.md: Updated to reflect v1 as main version with migration guidance
  • CHANGELOG.md: Added for v1 release tracking

New file structure

This is how the directory structure looks like:

image

chore: move next codebase to root and added migration guide

chore: update build-next.yml

chore: update eslint config

chore: ignore scripts on eslint
@antoniocapelo antoniocapelo marked this pull request as ready for review July 10, 2025 17:21
@antoniocapelo antoniocapelo requested review from brennj, dragidavid, eng-almeida and sandrina-p and removed request for sandrina-p July 10, 2025 17:30
@antoniocapelo antoniocapelo merged commit dc41922 into main Jul 11, 2025
5 checks passed
@antoniocapelo antoniocapelo deleted the rmt-1698-move-next-to-root branch July 11, 2025 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants