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

[Tooling] Communicate component deprecations and upcoming removal via console #9295

Closed
2 of 8 tasks
geospatialem opened this issue May 9, 2024 · 4 comments
Closed
2 of 8 tasks
Assignees
Labels
4 - verified Issues that have been released and confirmed resolved. Calcite (dev) Issues logged by Calcite developers. calcite-components Issues specific to the @esri/calcite-components package. enhancement Issues tied to a new feature or request. estimate - 3 A day or two of work, likely requires updates to tests. impact - p1 - need for current milestone User set priority impact status of p1 - need for current milestone p - high Issue should be addressed in the current milestone, impacts component or core functionality p1 - need for current milestone User set priority status of p1 - need for current milestone

Comments

@geospatialem
Copy link
Member

geospatialem commented May 9, 2024

Check existing issues

Description

Communicate component deprecations and future major version targeted release for developers to start transition to other supported components.

Acceptance Criteria

If a component is deprecated, we communicate to developers:

  • its deprecation and
  • when the anticipated removal will take place (e.g., 3.0, 4.0, etc.)

Relevant Info

No response

Which Component

Will currently apply to:

  • Pick List: Pick List, Pick List Group, Pick List Item in 3.0
  • Value List: Value List, Value List Item in 3.0
  • Tip: Tip, Tip Group, Tip Manager in 4.0
  • Tile Select: Tile Select, Tile Select Group in 4.0

Example Use Case

No response

Priority impact

p1 - need for current milestone

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-angular
  • @esri/calcite-components-react
  • @esri/calcite-design-tokens
  • @esri/eslint-plugin-calcite-components

Esri team

Calcite (dev)

@geospatialem geospatialem added enhancement Issues tied to a new feature or request. p - high Issue should be addressed in the current milestone, impacts component or core functionality 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. labels May 9, 2024
@github-actions github-actions bot added impact - p1 - need for current milestone User set priority impact status of p1 - need for current milestone calcite-components Issues specific to the @esri/calcite-components package. Calcite (dev) Issues logged by Calcite developers. labels May 9, 2024
@geospatialem geospatialem removed the needs triage Planning workflow - pending design/dev review. label May 9, 2024
@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 Jul 1, 2024
@github-actions github-actions bot added the p1 - need for current milestone User set priority status of p1 - need for current milestone label Jul 19, 2024
@jcfranco jcfranco added 2 - in development Issues that are actively being worked on. estimate - 3 A day or two of work, likely requires updates to tests. and removed 1 - assigned Issues that are assigned to a sprint and a team member. labels Jul 19, 2024
@jcfranco jcfranco added 3 - installed Issues that have been merged to master branch and are ready for final confirmation. and removed 2 - in development Issues that are actively being worked on. labels Jul 23, 2024
@github-actions github-actions bot assigned geospatialem and DitwanP and unassigned jcfranco Jul 23, 2024
Copy link
Contributor

Installed and assigned for verification.

@geospatialem
Copy link
Member Author

Awesome, this going to be a great addition! @jcfranco It looks like there is one deprecation missing for the value-list-item in this codepen. Relaying this back over to ya to add in. 🕵🏻

@geospatialem geospatialem added 2 - in development Issues that are actively being worked on. and removed 3 - installed Issues that have been merged to master branch and are ready for final confirmation. labels Jul 24, 2024
@jcfranco jcfranco added 3 - installed Issues that have been merged to master branch and are ready for final confirmation. and removed 2 - in development Issues that are actively being worked on. labels Jul 26, 2024
Copy link
Contributor

Installed and assigned for verification.

@github-actions github-actions bot assigned DitwanP and unassigned jcfranco Jul 26, 2024
jcfranco added a commit that referenced this issue Jul 26, 2024
**Related Issue:** #9295 

## Summary

Add missing deprecation warning.
jcfranco added a commit that referenced this issue Jul 27, 2024
…ation messages (#9870)

**Related Issue:** #9295

## Summary

Fixes mismatched component names in deprecation warning.
@DitwanP
Copy link
Contributor

DitwanP commented Jul 27, 2024

🍡 Looks great! Verified locally on dev
image

@DitwanP DitwanP closed this as completed Jul 27, 2024
@DitwanP DitwanP added 4 - verified Issues that have been released and confirmed resolved. and removed 3 - installed Issues that have been merged to master branch and are ready for final confirmation. labels Jul 27, 2024
calcite-admin pushed a commit that referenced this issue Jul 30, 2024
**Related Issue:** #9295 

## Summary

Add missing deprecation warning.
calcite-admin pushed a commit that referenced this issue Jul 30, 2024
…ation messages (#9870)

**Related Issue:** #9295

## Summary

Fixes mismatched component names in deprecation warning.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4 - verified Issues that have been released and confirmed resolved. Calcite (dev) Issues logged by Calcite developers. calcite-components Issues specific to the @esri/calcite-components package. enhancement Issues tied to a new feature or request. estimate - 3 A day or two of work, likely requires updates to tests. impact - p1 - need for current milestone User set priority impact status of p1 - need for current milestone p - high Issue should be addressed in the current milestone, impacts component or core functionality p1 - need for current milestone User set priority status of p1 - need for current milestone
Projects
None yet
Development

No branches or pull requests

3 participants