I'd like to deprecate EuiToggle largely because it's an inaccessible pattern that requires more work to get right but having it bundled in the library gives it a air of authority.
I think it also aligns with EUI's ethos of not providing things that don't have use-cases. So, right now, this is a public API that we have upkeep expectations around even though no one has any reason to use so we can't even say this is the best solution we can offer.
After scouring GitHub, the only usage of it that I could find is EUI itself within EuiButtonToggle so it shouldn't have much (if any) impact on any consumers of EUI.
Given it's lack of usage, I don't think a better time to remove it will come up.
CC @snide @cchaos — thoughts?
I'd like to deprecate
EuiTogglelargely because it's an inaccessible pattern that requires more work to get right but having it bundled in the library gives it a air of authority.I think it also aligns with EUI's ethos of not providing things that don't have use-cases. So, right now, this is a public API that we have upkeep expectations around even though no one has any reason to use so we can't even say this is the best solution we can offer.
After scouring GitHub, the only usage of it that I could find is EUI itself within
EuiButtonToggleso it shouldn't have much (if any) impact on any consumers of EUI.Given it's lack of usage, I don't think a better time to remove it will come up.
CC @snide @cchaos — thoughts?