DSingh0304 commented on issue #3347: URL: https://github.com/apache/apisix-dashboard/issues/3347#issuecomment-4117310370
> Thanks for the detailed proposal and PoC ([#3346](https://github.com/apache/apisix-dashboard/pull/3346)). The phased breakdown and acceptance criteria are well-structured, which is helpful for GSoC evaluation. > > This direction is valuable. However, there's already a related PoC in [#3274](https://github.com/apache/apisix-dashboard/pull/3274) with deeper coverage (anyOf, if/then/else, encrypt_fields + 43 tests). > > To avoid duplicate efforts, I'd suggest focusing on: > > 1. Clarify how your approach aligns with / reuses [GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI #3274](https://github.com/apache/apisix-dashboard/pull/3274), rather than building two parallel engines > > 2. Prioritize correctness issues first (especially form state cleanup on branch switching, submit payload consistency) > > 3. Bind each phase to verifiable deliverables (test cases + reproducible demo + pass criteria) > > > If you're interested, consider posting an "alignment plan" in this issue: > > * Which parts of [GSOC 26 Proof of Concept: add SchemaForm component for JSON Schema to Form UI #3274](https://github.com/apache/apisix-dashboard/pull/3274) you plan to reuse > > * Which capabilities/tests you'll add > > * Minimum mergeable target (MVP gate) for each phase > > > This would make the proposal more compelling in the GSoC context. Thanks for the ping! I'm the author of #3274. Happy to collaborate and discuss where the implementations can align. The core engine is intentionally designed to be extensible. Feel free to open a discussion on that PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
