Find Devextreme Dist Examples and Templates
Use this online devextreme-dist playground to view and fork devextreme-dist example apps and templates on CodeSandbox. Click any example below to run it instantly or find templates that can be used as a pre-built solution!
DevExtreme EAP 23.2 - Form: Change Detection (Dirty State)This demo shows how to validate Form editors. To apply validation rules to an editor, declare them in the validationRules[] array. Specify type and other properties for each rule.
The following validation rules are shown in this demo:
RequiredRule
Requires that a validated editor has a value.
CompareRule
Compares the editor's value to the specified expression.
PatternRule
Checks whether an editor value matches a specified pattern.
RangeRule
Checks whether an editor value is in a specified range.
StringLengthRule
Requires that an editor value length is in a specified range.
EmailRule
Requires that an editor value matches the Email pattern.
AsyncRule
Allows you to add custom server-side validation logic. Rules of this type run last, only if all other rules passed. In this demo, an AsyncRule checks whether user input matches [email protected].
To submit form data, do the following:
Wrap the Form component in the HTML <form> element.
Use the Button Form Item to add a button to the form. This button submits the form data.
Enable the button's useSubmitBehavior property.
When users click the button, the Form validates all editors that belong to the same validationGroup as this button. In this demo, all these editors belong to the customerData group. Form data can be submitted to a server only if input validation is successful. Enable the showValidationSummary property to display all validation errors at the bottom of the Form.
Validation - DevExtreme Form (forked)This demo shows how to validate Form editors. To apply validation rules to an editor, declare them in the validationRules[] array. Specify type and other properties for each rule.
The following validation rules are shown in this demo:
RequiredRule
Requires that a validated editor has a value.
CompareRule
Compares the editor's value to the specified expression.
PatternRule
Checks whether an editor value matches a specified pattern.
RangeRule
Checks whether an editor value is in a specified range.
StringLengthRule
Requires that an editor value length is in a specified range.
EmailRule
Requires that an editor value matches the Email pattern.
AsyncRule
Allows you to add custom server-side validation logic. Rules of this type run last, only if all other rules passed. In this demo, an AsyncRule checks whether user input matches [email protected].
To submit form data, do the following:
Wrap the Form component in the HTML <form> element.
Use the Button Form Item to add a button to the form. This button submits the form data.
Enable the button's useSubmitBehavior property.
When users click the button, the Form validates all editors that belong to the same validationGroup as this button. In this demo, all these editors belong to the customerData group. Form data can be submitted to a server only if input validation is successful. Enable the showValidationSummary property to display all validation errors at the bottom of the Form.
Overview - DevExtreme Vector Map (forked)DevExtreme React Maps include two interactive UI components for creating GPS navigation maps and vector maps. The Map component works with Google Maps and Bing Maps API, supports roadmap, satellite, and hybrid views, and allows a user to create markers and routes. The Vector Map component comes with predefined data sources, a variety of colorization modes, and multiple legends. Advanced UI customization is carried out using template components and render props. Declared PropTypes for typechecking are included as well. Learn more about DevExtreme React components.
Validation - DevExtreme Form (forked)This demo shows how to validate Form editors. To apply validation rules to an editor, declare them in the validationRules[] array. Specify type and other properties for each rule.
The following validation rules are shown in this demo:
RequiredRule
Requires that a validated editor has a value.
CompareRule
Compares the editor's value to the specified expression.
PatternRule
Checks whether an editor value matches a specified pattern.
RangeRule
Checks whether an editor value is in a specified range.
StringLengthRule
Requires that an editor value length is in a specified range.
EmailRule
Requires that an editor value matches the Email pattern.
AsyncRule
Allows you to add custom server-side validation logic. Rules of this type run last, only if all other rules passed. In this demo, an AsyncRule checks whether user input matches [email protected].
To submit form data, do the following:
Wrap the Form component in the HTML <form> element.
Use the Button Form Item to add a button to the form. This button submits the form data.
Enable the button's useSubmitBehavior property.
When users click the button, the Form validates all editors that belong to the same validationGroup as this button. In this demo, all these editors belong to the customerData group. Form data can be submitted to a server only if input validation is successful. Enable the showValidationSummary property to display all validation errors at the bottom of the Form.
Zooming and Centering - DevExtreme Vector Map (forked)This demo shows the VectorMap zooming and centering capabilities. The map contains several cities represented by dot markers. To identify a city, pause on its marker, and the name of the city will appear in a tooltip. Moreover, if you click the marker, the map will be zoomed and centered on it. In code it is performed by calling the center(centerCoordinates) and zoomFactor(zoomFactor) methods. A click on the «Reset» button restores default center coordinates and zoom factor.
DevExtreme Beta 23.2 - Form: Change Detection (Dirty State)This demo shows how to validate Form editors. To apply validation rules to an editor, declare them in the validationRules[] array. Specify type and other properties for each rule.
The following validation rules are shown in this demo:
RequiredRule
Requires that a validated editor has a value.
CompareRule
Compares the editor's value to the specified expression.
PatternRule
Checks whether an editor value matches a specified pattern.
RangeRule
Checks whether an editor value is in a specified range.
StringLengthRule
Requires that an editor value length is in a specified range.
EmailRule
Requires that an editor value matches the Email pattern.
AsyncRule
Allows you to add custom server-side validation logic. Rules of this type run last, only if all other rules passed. In this demo, an AsyncRule checks whether user input matches [email protected].
To submit form data, do the following:
Wrap the Form component in the HTML <form> element.
Use the Button Form Item to add a button to the form. This button submits the form data.
Enable the button's useSubmitBehavior property.
When users click the button, the Form validates all editors that belong to the same validationGroup as this button. In this demo, all these editors belong to the customerData group. Form data can be submitted to a server only if input validation is successful. Enable the showValidationSummary property to display all validation errors at the bottom of the Form.
DevExtreme EAP 23.2 - Form: Change Detection (Dirty State) (forked)This demo shows how to validate Form editors. To apply validation rules to an editor, declare them in the validationRules[] array. Specify type and other properties for each rule.
The following validation rules are shown in this demo:
RequiredRule
Requires that a validated editor has a value.
CompareRule
Compares the editor's value to the specified expression.
PatternRule
Checks whether an editor value matches a specified pattern.
RangeRule
Checks whether an editor value is in a specified range.
StringLengthRule
Requires that an editor value length is in a specified range.
EmailRule
Requires that an editor value matches the Email pattern.
AsyncRule
Allows you to add custom server-side validation logic. Rules of this type run last, only if all other rules passed. In this demo, an AsyncRule checks whether user input matches [email protected].
To submit form data, do the following:
Wrap the Form component in the HTML <form> element.
Use the Button Form Item to add a button to the form. This button submits the form data.
Enable the button's useSubmitBehavior property.
When users click the button, the Form validates all editors that belong to the same validationGroup as this button. In this demo, all these editors belong to the customerData group. Form data can be submitted to a server only if input validation is successful. Enable the showValidationSummary property to display all validation errors at the bottom of the Form.
Overview - DevExtreme Vector Map (forked)DevExtreme React Maps include two interactive UI components for creating GPS navigation maps and vector maps. The Map component works with Google Maps and Bing Maps API, supports roadmap, satellite, and hybrid views, and allows a user to create markers and routes. The Vector Map component comes with predefined data sources, a variety of colorization modes, and multiple legends. Advanced UI customization is carried out using template components and render props. Declared PropTypes for typechecking are included as well. Learn more about DevExtreme React components.
Colors Customization - DevExtreme Vector Map (forked)This demo shows how to color different map elements. The map represented here indicates the top ten largest countries in the world by means of colors. These colors are assigned to the map areas using the customize callback function of the layers object. Moreover, when one of the areas is selected or hovered over, its color changes to those specified by the selectedColor and hoveredColor properties.
Tooltips for the map areas representing the largest countries are customized as well. Using the tooltip | customizeTooltip callback function, they are colored identical to the areas themselves and display the total area of the country.
DevExtreme EAP 23.2 - Form: Change Detection (Dirty State) (forked)This demo shows how to validate Form editors. To apply validation rules to an editor, declare them in the validationRules[] array. Specify type and other properties for each rule.
The following validation rules are shown in this demo:
RequiredRule
Requires that a validated editor has a value.
CompareRule
Compares the editor's value to the specified expression.
PatternRule
Checks whether an editor value matches a specified pattern.
RangeRule
Checks whether an editor value is in a specified range.
StringLengthRule
Requires that an editor value length is in a specified range.
EmailRule
Requires that an editor value matches the Email pattern.
AsyncRule
Allows you to add custom server-side validation logic. Rules of this type run last, only if all other rules passed. In this demo, an AsyncRule checks whether user input matches [email protected].
To submit form data, do the following:
Wrap the Form component in the HTML <form> element.
Use the Button Form Item to add a button to the form. This button submits the form data.
Enable the button's useSubmitBehavior property.
When users click the button, the Form validates all editors that belong to the same validationGroup as this button. In this demo, all these editors belong to the customerData group. Form data can be submitted to a server only if input validation is successful. Enable the showValidationSummary property to display all validation errors at the bottom of the Form.
Validation - DevExtreme Form (forked)This demo shows how to validate Form editors. To apply validation rules to an editor, declare them in the validationRules[] array. Specify type and other properties for each rule.
The following validation rules are shown in this demo:
RequiredRule
Requires that a validated editor has a value.
CompareRule
Compares the editor's value to the specified expression.
PatternRule
Checks whether an editor value matches a specified pattern.
RangeRule
Checks whether an editor value is in a specified range.
StringLengthRule
Requires that an editor value length is in a specified range.
EmailRule
Requires that an editor value matches the Email pattern.
AsyncRule
Allows you to add custom server-side validation logic. Rules of this type run last, only if all other rules passed. In this demo, an AsyncRule checks whether user input matches [email protected].
To submit form data, do the following:
Wrap the Form component in the HTML <form> element.
Use the Button Form Item to add a button to the form. This button submits the form data.
Enable the button's useSubmitBehavior property.
When users click the button, the Form validates all editors that belong to the same validationGroup as this button. In this demo, all these editors belong to the customerData group. Form data can be submitted to a server only if input validation is successful. Enable the showValidationSummary property to display all validation errors at the bottom of the Form.
Tooltips (forked)To set the tooltip's content, specify the contentTemplate. Inside the template, you can identify the map area or marker for which the tooltip is displayed and thus display information related to that map element.
In this demo, the contentTemplate property is used to display the PieChart component in the tooltip.
