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 #304

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

Adds a deprecation warning to the auro-datepicker component and updates the documentation to reflect its deprecated status. This change informs users that the component is no longer supported and encourages migration to the new Auro Formkit.

Documentation:

  • Adds a deprecation warning to the README and other documentation files.
  • Updates the documentation build process to use a custom script for deprecated components.

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:08
@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-datepicker component and updates the documentation generation process to handle deprecated components. It introduces a new documentation template and a custom script to generate documentation that includes the deprecation notice.

Updated class diagram for deprecatedDocsProcessor

classDiagram
  class processDocFiles{
    +config
  }
  class fileConfigs{
    +identifier
    +input
    +output
    +mdMagicConfig
    +preProcessors
  }
  class templateFiller{
    +formatApiTable()
    +extractNames()
  }
  class Logger{
    +log(message)
    +error(message)
  }

  processDocFiles -- fileConfigs : uses
  processDocFiles -- templateFiller : uses
  processDocFiles -- Logger : uses
Loading

File-Level Changes

Change Details Files
Added a deprecation warning to the README, informing users that the component is no longer supported and recommending migration to Auro Formkit.
  • Added a warning message indicating deprecation.
  • Recommended migrating to Auro Formkit.
README.md
Updated the build process to use a custom script for generating documentation for deprecated components.
  • Replaced the standard documentation build script with deprecatedDocsProcessor.js.
package.json
Created a new template for generating README files for deprecated components, including a deprecation warning.
  • Added a template file for deprecated components.
  • Included a prominent deprecation warning in the template.
  • Ensured the template includes standard documentation sections.
docTemplates/README.md
Implemented a custom script to process documentation files for deprecated components, adapting the standard documentation generation process.
  • Created a new script deprecatedDocsProcessor.js.
  • Configured the script to process README, index, and API documentation files.
  • Added logic to handle file processing and error logging.
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 - here's some feedback:

Overall Comments:

  • Consider adding a script to automatically update the year in the deprecation warning message in README.md and docTemplates/README.md.
  • It might be helpful to include the date of deprecation in the deprecation warning.
Here's what I looked at during the review
  • 🟡 General issues: 1 issue found
  • 🟢 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.

Comment on lines +61 to +65
processDocFiles({ overwriteLocalCopies: false })
.then(() => {
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 (bug_risk): Revisit the intentional throwing of a testing error in production code.

The explicit throw of "TESTING ERROR" will always trigger the catch block and may be left over from debugging. Confirm if this behavior is intended or if it should be removed or conditioned on a debug flag.

Suggested change
processDocFiles({ overwriteLocalCopies: false })
.then(() => {
throw new Error("TESTING ERROR");
Logger.log("Docs processed successfully");
})
processDocFiles({ overwriteLocalCopies: false })
.then(() => {
if (process.env.NODE_ENV !== 'production') {
throw new Error("TESTING ERROR");
}
Logger.log("Docs processed successfully");
})

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