Mixed support

[kchobantonov]

1. provide support for mixed types
2. fix clearing of inputs when not under an object - e.g. string once cleared will become empty string rather than to return undefined to remove the property from the parent object
3. fix date controls, now the date can show year, year/month and etc. depending on the control option views
4. improve the performance to convert dayjs format into maska format function
5. fixing the :key to at least have the collection size into the key so when the size changes the vue will not reuse html elements leaving attributes like id unchanged
6. add more examples to show how the mixed control can be used
7. use arraySchema from the mapped values rather than using Resolve
8. minor UI changes to use less space
9. core changes : use the provided schema when the resolve failed, make sure that boolean is valid schema as well - e.g. items: true is valid schema (Note: the last change for the items to be boolean was reverted back since more code should be adjusted - maybe a future improvement)
10. introduce a new config - allowAdditionalPropertiesIfMissing - this allows to show the additioanalProperties UI when the additionalProperties and patternProperties do not exist. The reason is that by default if the additionalProperties is missing from the schema the default should be considered as true but the UI component does not respect that default - e.g. it needs to be explicitly states as additionalProperties: true if the UI control is needed without the allowAdditionalPropertiesIfMissing config

[kchobantonov]

@sdirix check my responses and also updated repo but it looks like the build failed perhaps because netlify is using greater than pnpm version 8 now ?

[sdirix]

I have concerns about the proposed changes to the core functionality.

Please have a look at my new comments and the unresolved comments from my previous review.

[kchobantonov]

@sdirix please review again - here are the outstanding items that I need to check with you if you are ok with those as they are at the moment with the explanation that was provided.

1. change in the packages/core/src/util/resolvers.ts - I have added the reason why is that but I haven't yet resolved the conversation
2. the changes to the :key to include the size of the layout items is still there at least until there is some support from the core to know when the uischema is changes to use the proper key that will work on all changes to the layout data - e.g. reordering and etc.
3. the issue where when we want to clear an input that is part of the additionalProperties (e.g. dynamic) and the type is an enum that we use an empty string as a reset value - not sure at the moment how to handle that one with a valid enum value since clearing does not necessary means to select any of the valid values from the supported enum set. Before that this change was not needed but then we were having an issue when we wanted to set the JSON as a data and that to be reflected by the UI - e.g. removing a dynamic field from the JSON and applying that to the form was not having an effect - that is why this change with what to set the value when the control clears the value was needed

[sdirix]

Works good for me!

I'm waiting on Lucas' (or your) input to this suggestion and the handling of the additionalErrors. When they are resolved I'm happy to merge.

Thanks for your great work and patience ;)

Nitpick: the "Mixed" and "Json Editor" examples in the Vue Vuetify app do not render as nicely as the other examples. Does not need to be resolved for the merge.

[sdirix]

@kchobantonov Please adapt the resolver as suggested and the additionalErrors, then we can merge

[kchobantonov]

@sdirix both changes that were request are now done - please review again and let me know if anything else is needed. Thanks for your feedback.

[kchobantonov]

@sdirix please review again - all concerns should be addresses and the last commit is fixing an issue where in the jsonschema example when you try to add new example field as an object and you do enable from the "Allow Additional Properties By Default" option then to correctly determine the type of the new properties that are going to be added to this new object example.