Skip to content
This repository was archived by the owner on Mar 7, 2025. It is now read-only.

DEPRECATION: add deprecation warning to this package #225

Closed

Conversation

DukeFerdinand
Copy link
Contributor

@DukeFerdinand DukeFerdinand commented Mar 6, 2025

Resolves AlaskaAirlines/auro-formkit#394, adding deprecation warning to old form element repositories.

Summary by Sourcery

Deprecates the auro-combobox component and adds a warning message to the documentation, advising users to migrate to the new Auro Formkit.

Documentation:

  • Adds a deprecation warning to the README, advising users to migrate to the new Auro Formkit.
  • Updates the documentation build process to use a custom script for deprecated components.
  • Updates the location of the design tokens CSS file in the documentation to use the auro-classic version.

As part of the new formkit release, all old form element repositories are being deprecated.
@DukeFerdinand DukeFerdinand requested a review from a team as a code owner March 6, 2025 23:07
@DukeFerdinand DukeFerdinand self-assigned this Mar 6, 2025
Copy link

sourcery-ai bot commented Mar 6, 2025

Reviewer's Guide by Sourcery

This pull request adds a deprecation warning to the auro-combobox component and updates the documentation generation process to handle deprecated components. The deprecation warning informs users that the component is no longer supported and directs them to migrate to the new Auro Formkit.

Updated class diagram for auro-combobox

classDiagram
  class auro_combobox {
    +DEPRECATED
    +warningMessage: string
    +migrateTo: string
  }
  note for auro_combobox "This component is deprecated and is no longer supported. Please migrate to the new Auro Formkit."
Loading

File-Level Changes

Change Details Files
Adds a deprecation warning to the combobox component.
  • Adds a deprecation warning to the top of the README.
  • The warning message informs users that the component is deprecated and links to the new Auro Formkit.
  • Updates the link to the design tokens CSS to point to the auro-classic version.
README.md
Updates the documentation generation process to handle deprecated components.
  • Creates a new documentation template specifically for deprecated components.
  • Updates the build:docs script in package.json to use the new deprecatedDocsProcessor.js script.
  • Creates a new script deprecatedDocsProcessor.js to handle the documentation generation for deprecated components.
package.json
docTemplates/README.md
packageScripts/deprecatedDocsProcessor.js

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

github-actions bot commented Mar 6, 2025

Surge demo deployment failed! 😭

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @DukeFerdinand - I've reviewed your changes and found some issues that need to be addressed.

Blocking issues:

  • Unexpected error thrown in promise resolution. (link)

Overall Comments:

  • Consider adding a step to the release process that archives the deprecated repo.
  • It might be helpful to include the date of deprecation in the warning message.
Here's what I looked at during the review
  • 🔴 General issues: 1 blocking issue, 2 other issues
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Complexity: all looks good
  • 🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

} from "@aurodesignsystem/auro-library/scripts/utils/sharedFileProcessorUtils.mjs";


export const fileConfigs = () => [
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue: Avoid hard-coded absolute paths in fileConfigs.

The file configuration uses absolute paths specific to one developer environment, which could cause issues in other environments or during deployment. Consider switching to relative or configurable paths to improve portability.

Comment on lines +61 to +62
processDocFiles({ overwriteLocalCopies: false })
.then(() => {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue (bug_risk): Unexpected error thrown in promise resolution.

After successfully processing document files, the code immediately throws an error ('TESTING ERROR'), which prevents further execution and appears to be leftover debugging. Remove or comment out this error before deploying.

// setup
await templateFiller.extractNames();

for (const fileConfig of fileConfigs(config)) {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: Unused 'config' parameter in fileConfigs function.

The function fileConfigs is defined without any parameters, yet it is being called with a config argument inside processDocFiles. Either update fileConfigs to accept and utilize the config or remove the parameter from the call.

Suggested change
for (const fileConfig of fileConfigs(config)) {
for (const fileConfig of fileConfigs()) {

Comment on lines +63 to +64
throw new Error("TESTING ERROR");
Logger.log("Docs processed successfully");
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion (code-quality): Remove unreachable code. (remove-unreachable-code)

Suggested change
throw new Error("TESTING ERROR");
Logger.log("Docs processed successfully");
throw new Error("TESTING ERROR");


ExplanationStatements after a return, break, continue or throw will never be executed.
Leaving them in the code confuses the reader, who may believe that these
statements have some effect. They should therefore be removed.

@DukeFerdinand DukeFerdinand deleted the deprecations/2025_03_05_add_deprecation_warnings branch March 6, 2025 23:39
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

formkit deprecate old form components in respective docs
1 participant