mirror of
https://github.com/sourcegraph/sourcegraph.git
synced 2026-02-06 19:21:50 +00:00
527503fead
* add graphql mutation to set repos on code hosts * add tests * remove debugging log * address feedback in pr #16841 * run go generate * set a response body on mocked http roundtripper for repo updater |
||
|---|---|---|
| .. | ||
| aws_codecommit_stringdata.go | ||
| aws_codecommit.schema.json | ||
| bitbucket_cloud_stringdata.go | ||
| bitbucket_cloud.schema.json | ||
| bitbucket_server_stringdata.go | ||
| bitbucket_server_utils.go | ||
| bitbucket_server.schema.json | ||
| campaign_spec_stringdata.go | ||
| campaign_spec.schema.json | ||
| changeset_spec_stringdata.go | ||
| changeset_spec.schema.json | ||
| extension_schema.go | ||
| gen.go | ||
| gen.sh | ||
| github_stringdata.go | ||
| github.schema.json | ||
| gitlab_stringdata.go | ||
| gitlab.schema.json | ||
| gitolite_stringdata.go | ||
| gitolite.schema.json | ||
| json-schema-draft-07.schema.json | ||
| other_external_service_stringdata.go | ||
| other_external_service.schema.json | ||
| phabricator_stringdata.go | ||
| phabricator.schema.json | ||
| README.md | ||
| repo_setter.go | ||
| schema.go | ||
| settings_stringdata.go | ||
| settings.schema.json | ||
| site_stringdata.go | ||
| site.schema.json | ||
| stringdata.go | ||
| tsconfig.json | ||
Sourcegraph JSON Schemas
JSON Schema is a way to define the structure of a JSON document. It enables typechecking and code intelligence on JSON documents.
Sourcegraph uses the following JSON Schemas:
settings.schema.jsoncritical.schema.jsonsite.schema.jsonextension.schema.json(not codegenned into Go structs)
Modifying a schema
- Edit the
*.schema.jsonfile in this directory. - Run
go generateto update the*_stringdata.jsonfile. - Commit the changes to both files.
- When the change is ready for release, update the documentation.
Known issues
- The JSON Schema IDs (URIs) are of the form
https://sourcegraph.com/v1/*.schema.json#, but these are not actually valid URLs. This means you generally need to supply them to JSON Schema validation libraries manually instead of having the validator fetch the schema from the web.