Detail

If no config is provided, then month, year and day should be selectable from calendar view by default

Detail

If we use metaAPI from @manojadams/metaforms-core package, it is not working as expected.

Expected

metaAPI methods should work fine and should be able to manipulate and update the form elements

Actual Result

update calls on metaAPI methods not updating the fields used in mui-forms

Type: feature

• Current checkbox allows only one value to be selected at present.
• Current select option allows only one value to be selected at present. It should be configurable to allow multiple values.

Above two behaviours are basic behaviours that must be supported in the controls.

Test and improve accessibility of current form fields.

Add name attribute for all controls.

Currently it is coming empty

Getting undefined with proper schema when section layout is selected as wizard:

Schema used:

{ "fields": [{ "name": "basic-details", "meta": { "type": "section", "displayName": "Basic Details" }, "fields": [ { "name": "firstName", "meta": { "displayName": "First Name", "displayType": "text", "displayProps": { "md": 6 } } }, { "name": "lastName", "meta": { "displayName": "Last Name", "displayType": "text", "displayProps": { "md": 6 } } }, { "name": "dob", "meta": { "displayName": "Date of Birth", "displayType": "date", "displayProps": { "md": 6 } } }, { "name": "phone", "meta": { "displayName": "Phone Number", "displayType": "text", "displayProps": { "md": 6 } } }, { "name": "email", "meta": { "displayName": "Email", "displayType": "email" } } ] }, { "name": "address-details", "meta": { "type": "section", "displayName": "Address Details" }, "fields": [ { "name": "address", "meta": { "displayName": "Address", "displayType": "header" } }, { "name": "address_1", "meta": { "displayName": "House No / Street", "displayType": "text" } }, { "name": "address_2", "meta": { "displayName": "Landmark", "displayType": "text" } }, { "name": "state", "meta": { "displayName": "State", "displayType": "select", "options": [{ "label": "Assam", "value": "assam" }], "displayProps": { "md": 6 } } }, { "name": "zipcode", "meta": { "displayName": "Zipcode", "displayType": "text", "displayProps": { "md": 6 } } }, { "name": "country", "meta": { "displayName": "Country", "displayType": "select", "value": "INDIA", "isDisabled": true, "options": [{ "label": "India", "value": "INDIA" }], "displayProps": { "md": 6 } } } ] }] }

Type:
Able to select, update and delete file are basic behaviour that must be supported by file control.

Issue Description:
The "Get Started" button on the landing page is not clickable in the mobile view, preventing users from proceeding further into the application. Clicking the button does not trigger any action, rendering the user unable to access the app's main features.

Steps to Reproduce:

1. Open the application's landing page on a mobile device.
2. Attempt to click on the "Get Started" button.

Expected Behavior:
Clicking the "Get Started" button should lead users to the next step of the onboarding process or the main interface of the application.

Actual Behavior:
The "Get Started" button does not respond to clicks in the mobile view, and there is no visible indication that the button has been clicked.

Additional Information:

• This issue is specific to the mobile view.

Screenshots/Attachments:

Great work,

I am starting to use it and I can't manage to do something as simple as making the inputs not take up the entire width of the container but only what they need by default.

Thank you.

Components to have loader for loading states:

• Select control
• MultiSelect control
• Search control

Field update not working properly for fields if section layout is stepper.

I have assigned a state to the schema property, but when I change the value of one of the fields of that state, it is not reflected in the form.

I have tried to display this value on the screen in another component, and it does change there.

Is there anything special that needs to be done for the form to recognize changes in the schema property?

Thank you.

Checkbox should support boolean values from list of options:

For example:

[{
 "label": "Yes",
 "value": true
}, {
  "label": "No",
 "value": false
}]

Add or use third party phone control which can take following inputs:

• Country flags
• Country extension
• Custom validation function
• Material look and feel