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 function
toggle in your
codebase to manage the discharge of unfinished or experimental options.
As soon as the function is stay in manufacturing and dealing as anticipated, the subsequent
logical step is to scrub up the toggle and any associated logic.

As an example, think about the next code:

const information = featureToggle('feature-new-product-list') ?  title: 'Product'  : undefined;

As soon as the function is absolutely launched and now not wants a toggle, this
might be simplified to:

const information =  title: '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 function toggles (like
feature-search-result-refinement, which can nonetheless be in growth)
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 seems to be in an AST. You should use instruments like AST
Explorer to visualise how supply code and AST
are mapped. It’s useful to know the node sorts you are interacting
with earlier than making use of any modifications.

The picture beneath reveals the syntax tree when it comes to ECMAScript syntax. It
incorporates nodes like Identifier (for variables), StringLiteral (for the
toggle title), and extra summary nodes like CallExpression and
ConditionalExpression.

Determine 2: The Summary Syntax Tree illustration of the function toggle verify

On this AST illustration, the variable information is assigned utilizing a
ConditionalExpression. The take a look at a part of the expression calls
featureToggle('feature-new-product-list'). If the take a look at returns true,
the consequent department assigns title: 'Product' to information. If
false, the alternate department assigns undefined.

For a process with clear enter and output, I favor writing exams first,
then implementing the codemod. I begin by defining a detrimental case to
guarantee we don’t unintentionally change issues we wish to depart 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 known as inside an if assertion), implement that case, and
guarantee all exams cross.

This strategy aligns effectively with Check-Pushed Growth (TDD), even
when you don’t observe TDD frequently. 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 exams to confirm how the codemod
behaves:

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

defineInlineTest(
  remodel,
  ,
  `
  const information = featureToggle('feature-new-product-list') ?  title: 'Product'  : undefined;
  `,
  `
  const information =  title: 'Product' ;
  `,
  "delete the toggle feature-new-product-list in conditional operator"
);

The defineInlineTest perform from jscodeshift lets you outline
the enter, anticipated output, and a string describing the take a look at’s intent.
Now, working the take a look at with a standard jest command will fail as a result of the
codemod isn’t written but.

The corresponding detrimental case would make sure the code stays unchanged
for different function toggles:

defineInlineTest(
  remodel,
  ,
  `
  const information = featureToggle('feature-search-result-refinement') ?  title: 'Product'  : undefined;
  `,
  `
  const information = featureToggle('feature-search-result-refinement') ?  title: 'Product'  : undefined;
  `,
  "don't change different function toggles"
);

Writing the Codemod

Let’s begin by defining a easy remodel perform. Create a file
referred to as remodel.js with the next code construction:

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

  // manipulate the tree nodes right here

  return root.toSource();
;

This perform 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 are able to begin implementing the remodel steps:

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

Right here’s how we obtain this utilizing jscodeshift:

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

  // Discover ConditionalExpression the place the take a look at is featureToggle('feature-new-product-list')
  root
    .discover(j.ConditionalExpression, 
      take a look at: 
        callee:  title: "featureToggle" ,
        arguments: [ value: "feature-new-product-list" ],
      ,
    )
    .forEach((path) => 
      // Change the ConditionalExpression with the 'consequent'
      j(path).replaceWith(path.node.consequent);
    );

  return root.toSource();
;

The codemod above:

• Finds ConditionalExpression nodes the place the take a look at calls
  featureToggle('feature-new-product-list').
• Replaces your complete conditional expression with the resultant (i.e.,
title: 'Product' ), eradicating the toggle logic and leaving simplified code
  behind.

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

You’ll want to write down extra take a look at 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 gives a command-line
instrument that you should use to use the codemod and report the outcomes.

$ jscodeshift -t transform-name src/

After validating the outcomes, verify that every one useful exams nonetheless
cross and that nothing breaks—even when you’re introducing a breaking change.
As soon as happy, 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 will
considerably enhance code high quality and maintainability. As codebases
evolve, they typically accumulate technical debt, together with outdated function
toggles, deprecated strategies, or tightly coupled elements. Manually
refactoring these areas might be time-consuming and error-prone.

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

Refactoring an Avatar Part

Now, let’s have a look at a extra advanced instance. Suppose you’re working with
a design system that features an Avatar part tightly coupled with a
Tooltip. Each time a consumer passes a title prop into the Avatar, it
mechanically wraps the avatar with a tooltip.

Determine 3: A avatar part with a tooltip

Right here’s the present Avatar implementation:

import  Tooltip  from "@design-system/tooltip";

const Avatar = ( title, picture : AvatarProps) => 
  if (title) 
    return (
      <Tooltip content material=title>
        <CircleImage picture=picture />
      </Tooltip>
    );
  

  return <CircleImage picture=picture />;
;

The objective is to decouple the Tooltip from the Avatar part,
giving builders extra flexibility. Builders ought to be capable of resolve
whether or not to wrap the Avatar in a Tooltip. Within the refactored model,
Avatar will merely render the picture, and customers can apply a Tooltip
manually if wanted.

Right here’s the refactored model of Avatar:

const Avatar = ( picture : AvatarProps) => 
  return <CircleImage picture=picture />;
;

Now, customers can manually wrap the Avatar with a Tooltip as
wanted:

import  Tooltip  from "@design-system/tooltip";
import  Avatar  from "@design-system/avatar";

const UserProfile = () => 
  return (
    <Tooltip content material="Juntao Qiu">
      <Avatar picture="/juntao.qiu.avatar.png" />
    </Tooltip>
  );
;

The problem arises when there are tons of of Avatar usages unfold
throughout the codebase. Manually refactoring every occasion can be extremely
inefficient, so we are able to use a codemod to automate this course of.

Utilizing instruments like AST Explorer, we are able to
examine the part and see which nodes symbolize the Avatar utilization
we’re concentrating on. An Avatar part with each title and picture props
is parsed into an summary syntax tree as proven beneath:

Determine 4: AST of the Avatar part utilization

Writing the Codemod

Let’s break down the transformation into smaller duties:

• Discover Avatar utilization within the part tree.
• Test if the title prop is current.
• If not, do nothing.
• If current:
• Create a Tooltip node.
• Add the title to the Tooltip.
• Take away the title from Avatar.
• Add Avatar as a baby of the Tooltip.
• Change the unique Avatar node with the brand new Tooltip.

To start, we’ll discover all situations of Avatar (I’ll omit among the
exams, however it’s best to write comparability exams first).

defineInlineTest(
     default: remodel, parser: "tsx" ,
    ,
    `
    <Avatar title="Juntao Qiu" picture="/juntao.qiu.avatar.png" />
    `,
    `
    <Tooltip content material="Juntao Qiu">
      <Avatar picture="/juntao.qiu.avatar.png" />
    </Tooltip>
    `,
    "wrap avatar with tooltip when title is supplied"
  );

Much like the featureToggle instance, we are able to use root.discover with
search standards to find all Avatar nodes:

root
  .discover(j.JSXElement, 
    openingElement:  title:  title: "Avatar"  ,
  )
  .forEach((path) => 
    // now we are able to deal with every Avatar occasion
  );

Subsequent, we verify if the title prop is current:

root
  .discover(j.JSXElement, 
    openingElement:  title:  title: "Avatar"  ,
  )
  .forEach((path) => 
    const avatarNode = path.node;

    const nameAttr = avatarNode.openingElement.attributes.discover(
      (attr) => attr.title.title === "title"
    );

    if (nameAttr) 
      const tooltipElement = createTooltipElement(
        nameAttr.worth.worth,
        avatarNode
      );
      j(path).replaceWith(tooltipElement);
    
  );

For the createTooltipElement perform, we use the
jscodeshift API to create a brand new JSX node, with the title
prop utilized to the Tooltip and the Avatar
part as a baby. Lastly, we name replaceWith to
change the present path.

Right here’s a preview of the way it seems to be in
Hypermod, the place the codemod is written on
the left. The highest half on the appropriate is the unique code, and the underside
half is the remodeled consequence:

Determine 5: Run checks inside hypermod earlier than apply it to your codebase

This codemod searches for all situations of Avatar. If a
title prop is discovered, it removes the title prop
from Avatar, wraps the Avatar inside a
Tooltip, and passes the title prop to the
Tooltip.

By now, I hope it’s clear that codemods are extremely helpful and
that the workflow is intuitive, particularly for large-scale modifications the place
guide updates can be an enormous burden. Nevertheless, that is not the entire
image. Within the subsequent part, I’ll make clear among the challenges
and the way we are able to handle these less-than-ideal facets.