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
Describe the bug
A clear and concise description of what the bug is.
When having the visible labels option lower than the total number of labels and labels are collapsed (in LabelQuestion and MultiLabelQuestion), if enough labels are selected to see the total number at first sight, the component to expand / collapse shows 0+. This is not desirable and we should think of a better behavior and logic to avoid having to show this.
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
OS [e.g. iOS]:
Browser [e.g. chrome, safari]:
Argilla Version [e.g. 1.0.0]:
ElasticSearch Version [e.g. 7.10.2]:
Docker Image (optional) [e.g. argilla:v1.0.0]:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
When having the visible labels option lower than the total number of labels and labels are collapsed (in
LabelQuestion
andMultiLabelQuestion
), if enough labels are selected to see the total number at first sight, the component to expand / collapse shows0+
. This is not desirable and we should think of a better behavior and logic to avoid having to show this.To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: