8e37b8938c
Created 3 new components: <OsqueryOptionsPage /> , <OsqueryOptionsForm />, and <YamlAce /> The <OsqueryOptionsPage /> component is rendered at the new route /admin/osquery. The user navigates to this route by selecting the "Osquery Options" sub-navigation in the admin dropdown menu. On the Osquery Options page, the user is presented with a ACE editor filled with the current osquery options. The current osquery options are retrieved from the serve when the page component mounts. These current osquery options are stored in the osquery slice of state. Clicking "UPDATE OPTIONS" will trigger a form submit and hit the v1/kolide/spec/osquery_options endpoint if the yaml is valid. If the yaml is not valid, an error message is presented to the user with details on what the error is and where it occurred. If the yaml is valid, the osquery options will be updated even if the options haven't change. |
||
---|---|---|
.. | ||
admin | ||
ChangeEmailForm | ||
ChangePasswordForm | ||
ConfigurePackQueryForm | ||
ConfirmInviteForm | ||
ConfirmSSOInviteForm | ||
fields | ||
ForgotPasswordForm | ||
FormField | ||
InviteUserForm | ||
LabelForm | ||
LoginForm | ||
LogoutForm | ||
packs | ||
queries/QueryForm | ||
RegistrationForm | ||
ResetPasswordForm | ||
UserSettingsForm | ||
validators | ||
_styles.scss | ||
Form.jsx | ||
README.md |
Fleet Forms
Fleet Forms leverage the Form Higher Order Component to simplify implementation and state management. As a user fills out a form, the Form HOC collects the form data in state. When the form is submitted, the Form HOC calls the provided client-side validation function with the form data and, if valid, then calls the handleSubmit
prop with the form data. If the client-side validation function returns errors, those errors are stored in the Form HOC state and displayed in the form input where the input name matches the error key.
The Form HOC takes 3 parameters:
- Component Class: The Component Class is the individual form component. It is a React component that renders a form.
- Options Hash: The Options Hash accepts 2 options:
fields
: This option is an array of field name strings in the form.validate
: This option is a function that gets called with the form data to test validity of the form. The return value from the validate function is expected to be a Javascript object with avalid
key that has a boolean value signifying whether or not the form is valid, and anerrors
key that has a Javascript object value containing the client side validation errors.
type ValidateResponse = { valid: String, errors: Object }; const validate Function = (formData: Object): ValidateResponse => { ... };
The Form HOC renders with Component Class with additional props. The added props to the form are:
fields
: The fields prop is a Javascript object containing an object for eachfield
string passed to the Form HOC in thefields
array. Each field object contains the following:error
: A string containing client side validation errors from thevalidate
function or from theserverErrors
prop passed to the form.name
: The name of the form field.onChange
: A function used to handle change on a form field element. This function stores the value of the form field element in state, and then submits the form field element values when the form is submitted.value
: The value of the form field element.
Additionally, the Form HOC accepts the following props passed to the form instance:
serverErrors
: A Javascript object containing errors returned by the server. The key should be the name of the form field and the value should be the error message string. (Defaults to{}
).formData
: A Javascript object representing the entity that will populate the form with the entity's attributes. When updating an entity, pass the entity to the form as theformData
prop.handleSubmit
: A function that is called when the form is submitted. The function will be called with the form data if thevalidate
function is run without errors.onChangeFunc
: A function that is called when a form field is changed. It is passed 2 parameters, the form field name and value. This is useful for handling specific form field changes on the parent component.
Example:
// Defining the form
import Button from 'components/buttons/Button';
import Form from 'components/forms/Form';
import InputField from 'components/forms/fields/InputField';
class MyForm extends Component {
render () {
return (
<form onSubmit={this.props.handleSubmit}>
<InputField
{...this.props.fields.first_name}
/>
<InputField
{...this.props.fields.last_name}
/>
<Button type="submit" />
</form>
);
}
}
export default Form(MyForm, {
fields: ['first_name', 'last_name'],
validate: (formData) => {
return { errors: {}, valid: true };
},
});
// Rendering the form
import MyForm from 'components/forms/MyForm';
class MyFormPage extends Component {
handleSubmit = (formData) => {
console.log(formData);
}
render () {
return (
<div>
<MyForm handleSubmit={this.handleSubmit} />
</div>
);
}
}
export default MyFormPage