react-jsonschema-form VS sourcegraph

I've been very passionate about a project called react-jsonschema-form (github, editor). I personally hate writing forms, and love the idea of serializable components, schema, validation all in one. I've always wanted an alternative to this project that offered an alternative to react, and possibly the ability to render a schema form to static HTML (like ssg).

See their playground app for examples of creating schema driven forms in no time.

I've tried with https://github.com/rjsf-team/react-jsonschema-form ,but the performance is poor when dealing with deep nested form with many inputs.

For example, I had a requirement for my team recently to be able to build dynamic form UIs, based off a JSON schema. There are heaps of javscript frameworks for this task e.g. react-jsonschema-form, but nothing in nuget or Blazor is going to help there. So you'd have to write all the logic yourself.

React-json-schema form has plenty of tests, using... it looks like react-dom/test-utils

https://github.com/rjsf-team/react-jsonschema-form

YAML-LD (application/ld+yaml) round-trips to JSON-LD (application/ld+json) which round trips to RDF; so W3C Linked Data Signatures / W3C Verified Claims cryptographic signatures verify regardless of graph representation.

YAML-LD > 3.1 JSON vs YAML comparison: https://json-ld.github.io/yaml-ld/spec/#json-vs-yaml

React Json Schema Form: https://github.com/rjsf-team/react-jsonschema-form

The most popular package it is being used in currently is react-jsonschema-form, which currently has 11,876 stars on GitHub

When I used react I used react-jsonschema-form which was awesome. Instead of writing inputs and forms I wrote the shape of that form in schema (or better yet, had my server send the shape of the form from the endpoint so that the front end required no coding). Unfortunately the vue equivalents never got ported to vue3 (and seem abandoned), so I wrote my own. Now I write stuff like:

Sourcegraph | REMOTE | Full-Time | Machine Learning Engineer, Developer Advocate, Enterprise Product Manager, Technical Advisor | https://sourcegraph.com

Sourcegraph is a code AI platform that makes it easy to read, write, and fix code–even in big, complex codebases.

We are building Cody, an AI coding assistant that uses code search and code intelligence to help devs quickly understand what's happening in code and generate new code that matches the best practices in your codebase. Cody supports AI-enabled autocompletion, fixing bugs, refactoring, test generation, code explanation, and answering high-level questions. You can read Steve Yegge's post on why Cody's code context engine differentiates it from the fast-moving field of AI dev tools: https://about.sourcegraph.com/blog/cheating-is-all-you-need.

Apply here: https://grnh.se/0572f98b4us

That's pretty much what https://sourcegraph.com/ are selling, is it not?

Despite their shitty rug-pull <https://github.com/sourcegraph/sourcegraph/pull/53345>, I do really like Sourcegraph and one doesn't (currently?!) need to be logged in to use it: https://sourcegraph.com/search and they have a handy rewrite pattern such that one can just plug the repo path into the URL for quick searching e.g. https://sourcegraph.com/github.com/JetBrains/intellij-commun...

- https://sourcegraph.com is pivoting and building a copilot application (named Cody). This is pretty good, since sourcegraph is great at understanding your code

While a readable Dockerfile can work as documentation, there are a few caveats:

* the application needs to be designed to work outside containers (so, no hardcoded URLs, ports, or paths). Also, not directly related to containers, but it's nice if it can be easily compiled in most environments and not just on the base image.

* I still need a way to notify me of updates; if the Dockerfile just wgets a binary, this doesn't help me.

* The Dockerfiles need to be easy to find. Sourcegraph's don't seem to be referenced from the documentation, I had to look through their Github repos to find https://github.com/sourcegraph/sourcegraph/tree/main/docker-... (though most are bazel scripts instead of Dockerfiles, but serve the same purpose)

We use Sourcegraph, which is a tool that searches through code in repositories. We leverage this tool in order to understand the adoption curve of our components across all of Reddit. We have a dashboard for each of the platforms to compare the inclusion of RPL components over legacy components. These insights are helpful for us to make informed decisions on how we continue to drive RPL adoption. We love seeing the green line go up and the red line go down!

SourceGraph: https://github.com/sourcegraph/sourcegraph/pulls?q=is%3Apr+a...