You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Each platform has its own details page, and almost all of them have a set of buttons that bring to the same or similar links. At the moment, each page has a copy of the buttons row that stands on its own, repeated dozens of times.
Describe the solution you'd like
Goal is to create an include that accepts a few props, that renders the row. This way the repeated code would be removed and everything could be managed in the new component, making it quicker and easier to add new things as needed.
Hi @smonolo , according to the problem described, we need a component for a row of buttons that takes a few props and that we can reuse in different components. Is it correct?
You are correct. As you can guess from what's described above, most software pages share a similar row of buttons. They are being placed in each file as a copy paste, and it would be nice to have a shared component that displays these buttons and takes a few props that will be passed by the software file itself, such as slackChannelLink for the software-specific Slack channel link, and so on.
It should be doable easily, but not sure how it would work with MD files. Feel free to ping me again if you have any questions.
Is your feature request related to a problem? Please describe.
Each platform has its own details page, and almost all of them have a set of buttons that bring to the same or similar links. At the moment, each page has a copy of the buttons row that stands on its own, repeated dozens of times.
Describe the solution you'd like
Goal is to create an include that accepts a few props, that renders the row. This way the repeated code would be removed and everything could be managed in the new component, making it quicker and easier to add new things as needed.
Describe alternatives you've considered
N/A
Additional context
18app details page:
The text was updated successfully, but these errors were encountered: