new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Mantine · all subjects

input/wrapper

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Input.Wrapper not needed when using specialized inputs

Input.Wrapper is already included in all specialized input components like TextInput, NativeSelect, and Textarea. Users do not need to manually wrap these inputs. Input.Wrapper should only be used when creating custom inputs.

inputWrapperOrder configures wrapper parts order

The inputWrapperOrder prop allows configuring the order of Input.Wrapper parts. It accepts an array of four elements: 'label', 'input', 'error', and 'description'. Not all parts are required to be included. Parts that are not included in the array will not be rendered.

inputContainer prop enhances inputs using Input.Wrapper

The inputContainer prop can be used with inputs that use Input.Wrapper under the hood, such as TextInput. This allows enhancing the input, for example by adding a Tooltip when the input is focused.

Give your agent this brain