We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We have too many "Accordian" components that roughly mirror each other with a lot of copy-pasta. Here is where consolidation was proposed.
We should have just one Accordion Component (without the typo) that handles all of our current use cases, including nested tables.
Because the value for a KeyValuePair is any, it should be possible to have KeyValuePair[] with string | number | AccordionProps as the value type.
value
KeyValuePair
any
KeyValuePair[]
string | number | AccordionProps
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Problem - what in Jaeger blocks you from solving the requirement?
We have too many "Accordian" components that roughly mirror each other with a lot of copy-pasta. Here is where consolidation was proposed.
Proposal - what do you suggest to solve the problem or improve the existing situation?
We should have just one Accordion Component (without the typo) that handles all of our current use cases, including nested tables.
Any open questions to address
Because the
value
for aKeyValuePair
isany
, it should be possible to haveKeyValuePair[]
withstring | number | AccordionProps
as the value type.The text was updated successfully, but these errors were encountered: