Refactoring with Codemods to Automate API Adjustments

Clear a Stale Characteristic Toggle

Let’s begin with a easy but sensible instance to show the
energy of codemods. Think about you’re utilizing a characteristic
toggle in your
codebase to regulate the discharge of unfinished or experimental options.
As soon as the characteristic is reside in manufacturing and dealing as anticipated, the subsequent
logical step is to wash up the toggle and any associated logic.

As an example, contemplate the next code:

const knowledge = featureToggle('feature-new-product-list') ? { identify: 'Product' } : undefined;

As soon as the characteristic is totally launched and now not wants a toggle, this
will be simplified to:

const knowledge = { identify: 'Product' };

The duty entails discovering all situations of featureToggle within the
codebase, checking whether or not the toggle refers to
feature-new-product-list, and eradicating the conditional logic surrounding
it. On the similar time, different characteristic toggles (like
feature-search-result-refinement, which can nonetheless be in improvement)
ought to stay untouched. The codemod must perceive the construction
of the code to use modifications selectively.

Understanding the AST

Earlier than we dive into writing the codemod, let’s break down how this
particular code snippet appears in an AST. You should use instruments like AST
Explorer to visualise how supply code and AST
are mapped. It’s useful to grasp the node sorts you are interacting
with earlier than making use of any modifications.

The picture beneath reveals the syntax tree by way of ECMAScript syntax. It
incorporates nodes like Identifier (for variables), StringLiteral (for the
toggle identify), and extra summary nodes like CallExpression and
ConditionalExpression.

Determine 2: The Summary Syntax Tree illustration of the characteristic toggle examine

On this AST illustration, the variable knowledge is assigned utilizing a
ConditionalExpression. The check a part of the expression calls
featureToggle('feature-new-product-list'). If the check returns true,
the consequent department assigns { identify: 'Product' } to knowledge. If
false, the alternate department assigns undefined.

For a process with clear enter and output, I favor writing assessments first,
then implementing the codemod. I begin by defining a adverse case to
guarantee we don’t unintentionally change issues we wish to go away untouched,
adopted by an actual case that performs the precise conversion. I start with
a easy state of affairs, implement it, then add a variation (like checking if
featureToggle is named inside an if assertion), implement that case, and
guarantee all assessments move.

This strategy aligns effectively with Take a look at-Pushed Improvement (TDD), even
when you don’t observe TDD commonly. Figuring out precisely what the
transformation’s inputs and outputs are earlier than coding improves security and
effectivity, particularly when tweaking codemods.

With jscodeshift, you may write assessments to confirm how the codemod
behaves:

const rework = require("../remove-feature-new-product-list");

defineInlineTest(
  rework,
  {},
  `
  const knowledge = featureToggle('feature-new-product-list') ? { identify: 'Product' } : undefined;
  `,
  `
  const knowledge = { identify: 'Product' };
  `,
  "delete the toggle feature-new-product-list in conditional operator"
);

The defineInlineTest operate from jscodeshift permits you to outline
the enter, anticipated output, and a string describing the check’s intent.
Now, working the check with a traditional jest command will fail as a result of the
codemod isn’t written but.

The corresponding adverse case would make sure the code stays unchanged
for different characteristic toggles:

defineInlineTest(
  rework,
  {},
  `
  const knowledge = featureToggle('feature-search-result-refinement') ? { identify: 'Product' } : undefined;
  `,
  `
  const knowledge = featureToggle('feature-search-result-refinement') ? { identify: 'Product' } : undefined;
  `,
  "don't change different characteristic toggles"
);

Writing the Codemod

Let’s begin by defining a easy rework operate. Create a file
known as rework.js with the next code construction:

module.exports = operate(fileInfo, api, choices) {
  const j = api.jscodeshift;
  const root = j(fileInfo.supply);

  // manipulate the tree nodes right here

  return root.toSource();
};

This operate reads the file right into a tree and makes use of jscodeshift’s API to
question, modify, and replace the nodes. Lastly, it converts the AST again to
supply code with .toSource().

Now we will begin implementing the rework steps:

1. Discover all situations of featureToggle.
2. Confirm that the argument handed is 'feature-new-product-list'.
3. Exchange all the conditional expression with the consequent half,
   successfully eradicating the toggle.

Right here’s how we obtain this utilizing jscodeshift:

module.exports = operate (fileInfo, api, choices) {
  const j = api.jscodeshift;
  const root = j(fileInfo.supply);

  // Discover ConditionalExpression the place the check is featureToggle('feature-new-product-list')
  root
    .discover(j.ConditionalExpression, {
      check: {
        callee: { identify: "featureToggle" },
        arguments: [{ value: "feature-new-product-list" }],
      },
    })
    .forEach((path) => {
      // Exchange the ConditionalExpression with the 'consequent'
      j(path).replaceWith(path.node.consequent);
    });

  return root.toSource();
};

The codemod above:

• Finds ConditionalExpression nodes the place the check calls
  featureToggle('feature-new-product-list').
• Replaces all the conditional expression with the resultant (i.e., {
identify: 'Product' }), eradicating the toggle logic and leaving simplified code
  behind.

This instance demonstrates how simple it’s to create a helpful
transformation and apply it to a big codebase, considerably lowering
guide effort.

You’ll want to jot down extra check instances to deal with variations like
if-else statements, logical expressions (e.g.,
!featureToggle('feature-new-product-list')), and so forth to make the
codemod sturdy in real-world situations.

As soon as the codemod is prepared, you may check it out on a goal codebase,
such because the one you are engaged on. jscodeshift supplies a command-line
software that you need to use to use the codemod and report the outcomes.

$ jscodeshift -t transform-name src/

After validating the outcomes, examine that every one useful assessments nonetheless
move and that nothing breaks—even when you’re introducing a breaking change.
As soon as glad, you may commit the modifications and lift a pull request as
a part of your regular workflow.

Codemods Enhance Code High quality and Maintainability

Codemods aren’t simply helpful for managing breaking API modifications—they’ll
considerably enhance code high quality and maintainability. As codebases
evolve, they usually accumulate technical debt, together with outdated characteristic
toggles, deprecated strategies, or tightly coupled parts. Manually
refactoring these areas will be time-consuming and error-prone.

By automating refactoring duties, codemods assist preserve your codebase clear
and freed from legacy patterns. Recurrently making use of codemods permits you to
implement new coding requirements, take away unused code, and modernize your
codebase with out having to manually modify each file.