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
As a FE-Dev of Team Porta I'd like to fully commit to 'version everything' and as such utilize versioned components like sd-1-2-3-input and sd-1-2-3-popup when calling setupAutocomplete().
Currently,
setupAutocomplete() will create an unversioned sd-popup and apply styles to it, as well as styles depending on an unversioned sd-option.
Suggested Solution
Possibly make all elements configurable as a parameter, i.e. setupAutocomplete(myInputElement, myPopupElement, ...).
ℹ️ I do have a working implementation of that locally, but am currently unable to push back to Github :/
Subtasks
Design_implementation_task
Development_implementation_task
Design_release_task
DoR
Item has business value
Item all subtasks have been estimated by the team
Item is clear and well-defined
Item dependencies have been identified
DoD
All subtasks have been closed
The text was updated successfully, but these errors were encountered:
User Story
As a FE-Dev of Team Porta I'd like to fully commit to 'version everything' and as such utilize versioned components like
sd-1-2-3-input
andsd-1-2-3-popup
when callingsetupAutocomplete()
.Currently,
setupAutocomplete() will create an unversioned
sd-popup
and apply styles to it, as well as styles depending on an unversionedsd-option
.Suggested Solution
Possibly make all elements configurable as a parameter, i.e.
setupAutocomplete(myInputElement, myPopupElement, ...)
.Subtasks
DoR
DoD
The text was updated successfully, but these errors were encountered: