Is your feature request related to a problem? Please describe.
Currently, the "Previous" and "Next" navigation buttons have default classes (dp__btn dp--arrow-btn-nav) and do not support custom classes. This limitation hinders our ability to target these buttons individually in automated tests.
Describe the solution you'd like
Introduce two new props to assign custom classes to the "Previous" and "Next" navigation buttons. These props would allow developers to specify unique classes for each button, improving testability and customization.
Describe alternatives you've considered
Our current workaround involves targeting the common class dp--arrow-btn-nav. However, since both buttons share this class, our tests retrieve an array containing both buttons. This requires additional code to distinguish between the "Previous" and "Next" buttons, which is not ideal and adds unnecessary complexity.
Is your feature request related to a problem? Please describe. Currently, the "Previous" and "Next" navigation buttons have default classes (
dp__btn dp--arrow-btn-nav) and do not support custom classes. This limitation hinders our ability to target these buttons individually in automated tests.Describe the solution you'd like Introduce two new props to assign custom classes to the "Previous" and "Next" navigation buttons. These props would allow developers to specify unique classes for each button, improving testability and customization.
Describe alternatives you've considered Our current workaround involves targeting the common class
dp--arrow-btn-nav. However, since both buttons share this class, our tests retrieve an array containing both buttons. This requires additional code to distinguish between the "Previous" and "Next" buttons, which is not ideal and adds unnecessary complexity.