Calling Developers!
We are reenergizing our code contribution process! Learn More

What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Hello, I'd like to ask for a future proof safe way to add a column to a table in the backoffice GUI.

Options
U04V0L4ATAQ
U04V0L4ATAQ Posts: 11 🧑🏻‍🚀 - Cadet

Hello, I'd like to ask for a future proof safe way to add a column to a table in the backoffice GUI. My solution works, but I think it breaks some rules. I overrode configure and prepareData functions and added my new column, in the CompanyBusinessUnitGui module.

Comments

  • Alberto Reyer
    Alberto Reyer Lead Spryker Solution Architect / Technical Director Posts: 690 🪐 - Explorer
    Options

    That sounds perfectly fine.
    What rule do you think is broken by your change?

  • U04V0L4ATAQ
    U04V0L4ATAQ Posts: 11 🧑🏻‍🚀 - Cadet
    Options

    This was my first modification, and the naive solution was to override the functions. Was hoping there's a better way.

  • fsmeier
    fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,018 ⚖️ - Guardians (admin)
    Options

    Some Tables have table-extender plugin-stacks. This one not. But the ones with the extender-plugin-stack can very easy become a performance bottleneck. So overriding these two methods is in most cases the way to go (and use the parent whenever possible).