Skip to content
New issue

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

Enhancement: Add "hint-text" to calcite-label #2793

Closed
Tracked by #5529
bstifle opened this issue Aug 12, 2021 · 5 comments
Closed
Tracked by #5529

Enhancement: Add "hint-text" to calcite-label #2793

bstifle opened this issue Aug 12, 2021 · 5 comments
Assignees
Labels
1 - assigned Issues that are assigned to a sprint and a team member. design Issues that need design consultation prior to development. enhancement Issues tied to a new feature or request. estimate - 5 A few days of work, definitely requires updates to tests. p - high Issue should be addressed in the current milestone, impacts component or core functionality refactor Issues tied to code that needs to be significantly reworked.
Milestone

Comments

@bstifle
Copy link

bstifle commented Aug 12, 2021

Description

Add hint-text property to calcite-label

Acceptance Criteria

need text separate from calcite-message and calcite label to solve for static support text

Relevant Info

Could be neat to use for character count requirements

Which Component

calcite-label

Example Use Case

Hint stuff

@bstifle bstifle added enhancement Issues tied to a new feature or request. 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. labels Aug 12, 2021
@driskull
Copy link
Member

This might be better as a slot than a property I think.

@julio8a julio8a removed the needs triage Planning workflow - pending design/dev review. label Sep 24, 2021
@julio8a julio8a added this to the Freezer milestone Sep 24, 2021
@julio8a julio8a added the design Issues that need design consultation prior to development. label Sep 24, 2021
@julio8a
Copy link

julio8a commented Sep 24, 2021

This still needs more design for different layouts on input, i.e. inline.

@geospatialem geospatialem added 1 - assigned Issues that are assigned to a sprint and a team member. and removed 0 - new New issues that need assignment. labels Nov 7, 2022
@geospatialem geospatialem added refactor Issues tied to code that needs to be significantly reworked. 0 - new New issues that need assignment. and removed 1 - assigned Issues that are assigned to a sprint and a team member. labels Dec 2, 2022
@geospatialem
Copy link
Member

Adding the slot will require a major refactor, and will be prioritized after next month's release. cc: @ashetland, @Elijbet

Once prioritized the effort should be coupled with #4155 and #5079.

@geospatialem geospatialem added estimate - 5 A few days of work, definitely requires updates to tests. p - high Issue should be addressed in the current milestone, impacts component or core functionality labels Mar 3, 2023
@geospatialem geospatialem added 1 - assigned Issues that are assigned to a sprint and a team member. and removed 0 - new New issues that need assignment. labels Mar 3, 2023
@geospatialem
Copy link
Member

Follow-up includes:

@ashetland
Copy link
Contributor

Closing in favor of #5079 for inline slot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - assigned Issues that are assigned to a sprint and a team member. design Issues that need design consultation prior to development. enhancement Issues tied to a new feature or request. estimate - 5 A few days of work, definitely requires updates to tests. p - high Issue should be addressed in the current milestone, impacts component or core functionality refactor Issues tied to code that needs to be significantly reworked.
Projects
None yet
Development

No branches or pull requests

7 participants