Skip to content

Commit d888013

Browse files
Apply suggestions from code review
1 parent 353eba0 commit d888013

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

.prompts/project-info.prompttemplate

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ These UIs are targeted at entering, modifying and viewing data and are usually e
66
Any UI is defined by using two schemata:
77
- The JSON schema defines the underlying data to be shown in the UI (objects, properties, and their types)
88
- The UI schema defines how this data is rendered as a form, e.g. the order of controls, their visibility, and the layout.
9-
If no UI schema is given, it will be auto generated
9+
If no UI schema is given, JSON Forms generates one based on the given JSON schema.
1010

1111
We put great emphasis on the customizability and extensibility of JSON Forms.
1212

@@ -23,9 +23,9 @@ The JSON Forms mono repository consists of these packages:
2323
### Core principles
2424

2525
JSON Forms uses a reducer-style approach for its state management.
26-
The form-wide state is manipulated via the reducers in packages/core/src/reducers.
26+
The form-wide state is manipulated via the reducers in `packages/core/src/reducers`.
2727

28-
Renderers are registered in a registry, consisting of tester,renderer pairs.
28+
Renderers are registered in a registry, consisting of tester, renderer pairs.
2929
For each UI Schema element to be rendered, all testers are asked for their priority.
3030
The highest priority wins and the respective renderer gets full control over rendering.
3131
The renderer may dispatch back to JSON Forms to render children elements.

0 commit comments

Comments
 (0)