Primevue code pattern changes

UI Components for Vue
Post Reply
TDZTechnika
Posts: 13
Joined: 02 Jun 2020, 13:43

22 Feb 2021, 17:03

I cannot understand (or maybe I can) why are you guys switched to dynamic template rendering?
1. It is not readable.
2. Adds a lot of complexity (eg. dom rendering).
3. It is unstable, slow and easily bugs making

I still supporting primevue but it makes me feel the primevue is going into the rabbit hole with a lot of complexity and never-ending bugs.

I hope I am wrong. And vuejs is not reactjs.If I was a fan of dom rendering I would use reactjs.

Image
Last edited by TDZTechnika on 24 Feb 2021, 15:43, edited 3 times in total.

TDZTechnika
Posts: 13
Joined: 02 Jun 2020, 13:43

22 Feb 2021, 17:23

Another issue:. After the TabView/TabPanel changes the route-tag implementation becomes very complicated.

Now:

Code: Select all

<TabView :active-index="activeIndex"><TabPanel header="Main" /><TabPanel header="History" /></TabView>
Before:

Code: Select all

<TabView ><TabPanel header="Main" :active.sync="pageTabs.main" /><TabPanel header="History" :active.sync="pageTabs.history" /></TabView>
My url looked like this:
1. http://myapp.com/customers/customer?id=1#main
2. http://myapp.com/customers/customer?id=1#history

As an extra work after the changes it requires to match/link the tab index with the tag label. And it is still an issue as those tabs are constantly moved during the development so indexes needed to be fixed all time.
As you can see it adds another layer of complexity so I afraid everything becomes overcomplicated.

Don't understand why you make such decisions? Who decided to do this?

Post Reply

Return to “PrimeVue”

  • Information
  • Who is online

    Users browsing this forum: No registered users and 2 guests