Remove withTransportConfig wrapper

[m0ksem]

closes #1297 closes #1631 closes #1581

General

Patch instance props with vue reactive proxy. I looked in vue source code, Setup called, where we can access instance and patch it. Props in render function used from instance, so render function uses patched props. Same for DevTools. I believe using proxy is a nice approach, because we don't modify any object.

List of changes

• Patch vue instance props with Proxy that can return props from Vuestic Config,
• Patch class-component props
• Patch Options API component (added setup for patching props).

Test

• No unit tests until review and manual tests.
• Tested in build (can't see any difference).
• Demo link: http://localhost:8080/#/demo/va-config/VaConfig.demo.vue

Check this PR

• Vite build/serve 🤔
• Webpack serve/serve:productin/build ✔
• SSR Vite 🤔 - the only one difference I found from vue source code is that props are not reactive in SSR build. Shouldn't be a big difference with SPA builds.
• SSR Nuxt 😋 (later)

[Derranion]

VaAffix doesn't work. (works in the dev branch)

[Derranion]

VaConfig -> Global config works while using dev variables (yarn serve) But does not work in the production mode (yarn serve:production) same behavior we can expect after the build.

Steps to reproduce:

1. Press "Should set dark red color on click" button in the VaConfig
2. "Must change" should be red after this in production

Production mode:

Expected:

[Derranion]

VaToast is broken - does not show any toasts.

[Derranion]

VaDateInput text displays function body instead of expected visual representation of the date. Displayed function seems to not be executed.

[Derranion]

VaConfig local config does not update after change and uses default values instead.

Steps to repdoduce:

1. Change config color to any value.

[Derranion]

Please tell if you need some help or busy to update this.

[m0ksem]

@Derranion, pretty funny thing! 😁Nice catch.

withTransportConfigWrapper has resolved Function type as Object, But in vue docs I can see that Function type default value is resolved as Function, not like object fabric.

https://vuejs.org/guide/components/props.html#prop-validation

  // Function with a default value
  propG: {
    type: Function,
    // Unlike object or array default, this is not a factory function - this is a function to serve as a default value
    default() {
      return 'Default function'
    }
  }

I will change all components with () => () => result default value for Function props to () => result.

[m0ksem]

VaDateInput text displays function body instead of expected visual representation of the date. Displayed function seems to not be executed.

Marked all other comments with 🚀 reaction as resolved.

[m0ksem]

Usage of incorrect prop value inside of the Local config breaks component completely and makes it disappear.

Steps to reproduce:

1. Open `VaConfig` demo

2. In the `local config` color input field remove one symbol

3. Hover `VaButton` component.

It's correct behavior 😋, First, it wasn't disappearing on hover - #ff00 is cast to white color for some reason.
Having error during rendering process will stop component rendering. This issue is present even in develop.