<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: BezotCorp</title>
    <description>The latest articles on DEV Community by BezotCorp (bezotcorp).</description>
    <link>https://dev.to/bezotcorp</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Forganization%2Fprofile_image%2F15736%2F9ef0ea9b-4284-4b04-892e-f4fd0f184b2b.png</url>
      <title>DEV Community: BezotCorp</title>
      <link>https://dev.to/bezotcorp</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bezotcorp"/>
    <language>en</language>
    <item>
      <title>Introducing Standardizer: One Interface for Your Formatting Tools</title>
      <dc:creator>Bezot Rémi</dc:creator>
      <pubDate>Sat, 21 Nov 2026 12:23:57 +0000</pubDate>
      <link>https://dev.to/bezotcorp/introducing-standardizer-one-interface-for-your-formatting-tools-553h</link>
      <guid>https://dev.to/bezotcorp/introducing-standardizer-one-interface-for-your-formatting-tools-553h</guid>
      <description>&lt;p&gt;Software projects often rely on multiple tools to maintain consistent code formatting. Each language has its own ecosystem, its own commands, and sometimes its own integration requirements.&lt;/p&gt;

&lt;p&gt;For a project combining Rust, TypeScript, JavaScript, JSON, CSS or GraphQL, this can quickly become repetitive.&lt;/p&gt;

&lt;p&gt;At &lt;strong&gt;BezotCorp&lt;/strong&gt;, we're developing &lt;strong&gt;Standardizer&lt;/strong&gt;, an open-source command-line tool written in Rust, with a simple objective:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bring different standardization tools together behind a common interface, without replacing the tools that already work well.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The first public version focuses on code formatting and Git integration.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Standardizer?
&lt;/h2&gt;

&lt;p&gt;Modern development environments already have excellent specialized tools.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;rustfmt&lt;/code&gt; formats Rust code.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;Biome&lt;/code&gt; handles formatting across several web development languages.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The problem isn't necessarily the quality of these tools. It's the fragmentation of how we interact with them.&lt;/p&gt;

&lt;p&gt;Each tool has its own commands, configuration and supported formats. As projects grow, maintaining a consistent workflow across different technologies becomes more complicated.&lt;/p&gt;

&lt;p&gt;Standardizer approaches this differently: rather than implementing another formatter, it delegates work to existing specialized tools.&lt;/p&gt;

&lt;p&gt;This provides a common entry point while preserving their respective capabilities.&lt;/p&gt;

&lt;h2&gt;
  
  
  Getting started
&lt;/h2&gt;

&lt;p&gt;Standardizer is available on crates.io.&lt;/p&gt;

&lt;p&gt;Install it using Cargo:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;cargo install standardizer
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You can also download a prebuilt executable from the project's GitHub Releases page.&lt;/p&gt;

&lt;p&gt;Once installed, navigate anywhere inside a Git repository and run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;standardizer check
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This command checks supported files for formatting issues without modifying them.&lt;/p&gt;

&lt;p&gt;To apply formatting corrections:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;standardizer fix
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Standardizer delegates the work to the appropriate formatter and stages the files it actually modifies.&lt;/p&gt;

&lt;p&gt;Two commands, one entry point.&lt;/p&gt;

&lt;h2&gt;
  
  
  Supported tools and formats
&lt;/h2&gt;

&lt;p&gt;The current release integrates two formatting engines.&lt;/p&gt;

&lt;h3&gt;
  
  
  Rustfmt
&lt;/h3&gt;

&lt;p&gt;Rust source files are processed using &lt;code&gt;rustfmt&lt;/code&gt;, the standard formatting tool of the Rust ecosystem.&lt;/p&gt;

&lt;h3&gt;
  
  
  Biome
&lt;/h3&gt;

&lt;p&gt;Biome handles supported formats from the JavaScript and web development ecosystem, including:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;JavaScript and JSX&lt;/li&gt;
&lt;li&gt;TypeScript and TSX&lt;/li&gt;
&lt;li&gt;JSON and JSONC&lt;/li&gt;
&lt;li&gt;CSS&lt;/li&gt;
&lt;li&gt;GraphQL&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Standardizer selects the appropriate tool according to the file type.&lt;/p&gt;

&lt;p&gt;The routing configuration is embedded in the distributed executable, so projects don't need to create an additional routing file.&lt;/p&gt;

&lt;h3&gt;
  
  
  What happens when a tool is missing?
&lt;/h3&gt;

&lt;p&gt;Standardizer is designed to work with the tools relevant to each project.&lt;/p&gt;

&lt;p&gt;For example, you shouldn't have to install Biome merely because Standardizer supports it.&lt;/p&gt;

&lt;p&gt;When an external formatter isn't available, Standardizer reports a warning and skips the corresponding processing instead of making that formatter a mandatory dependency for every project.&lt;/p&gt;

&lt;h2&gt;
  
  
  Git-aware processing
&lt;/h2&gt;

&lt;p&gt;One of the important design choices behind Standardizer is its integration with Git.&lt;/p&gt;

&lt;p&gt;Formatting tools can sometimes modify files that a developer isn't ready to include in a commit.&lt;/p&gt;

&lt;p&gt;Standardizer takes the repository's index state into account.&lt;/p&gt;

&lt;p&gt;It processes regular files whose working-tree content matches the Git index.&lt;/p&gt;

&lt;p&gt;It skips:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Untracked files&lt;/li&gt;
&lt;li&gt;Deleted files&lt;/li&gt;
&lt;li&gt;Files with unstaged modifications&lt;/li&gt;
&lt;li&gt;Partially staged files&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It also refuses to run when unresolved conflicts exist in the Git index.&lt;/p&gt;

&lt;p&gt;When running &lt;code&gt;standardizer fix&lt;/code&gt;, only files actually changed by Standardizer are staged.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The objective is to respect the developer's existing Git workflow instead of indiscriminately formatting the entire working directory.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This is particularly useful when working on multiple changes simultaneously.&lt;/p&gt;

&lt;h2&gt;
  
  
  A broader vision
&lt;/h2&gt;

&lt;p&gt;Formatting is only the starting point.&lt;/p&gt;

&lt;p&gt;The long-term ambition behind Standardizer is to provide a unified interface for different aspects of software standardization, potentially including:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Formatting&lt;/li&gt;
&lt;li&gt;Linting&lt;/li&gt;
&lt;li&gt;Compliance checks&lt;/li&gt;
&lt;li&gt;Additional specialized validation tools&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These are future directions, not features claimed to be available in the current release.&lt;/p&gt;

&lt;p&gt;The idea is to create an extensible foundation where existing tools can remain specialized while developers benefit from a more consistent way to invoke them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Standardizer Common
&lt;/h2&gt;

&lt;p&gt;Alongside the executable, we're also publishing &lt;strong&gt;&lt;code&gt;standardizer-common&lt;/code&gt;&lt;/strong&gt;, a Rust library supporting the Standardizer ecosystem.&lt;/p&gt;

&lt;p&gt;Both projects are available independently on crates.io, with their own documentation and versioning.&lt;/p&gt;

&lt;p&gt;This separation reflects an important principle in our development approach at BezotCorp: building reusable components rather than coupling everything to a single executable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Open source and contributions
&lt;/h2&gt;

&lt;p&gt;Standardizer is developed openly under the &lt;strong&gt;Apache License 2.0&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;You can explore the source code, review the implementation, report issues or contribute through GitHub.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Resources:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/BezotCorp/standardizer" rel="noopener noreferrer"&gt;Standardizer on GitHub&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://crates.io/crates/standardizer" rel="noopener noreferrer"&gt;Standardizer on crates.io&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://crates.io/crates/standardizer-common" rel="noopener noreferrer"&gt;Standardizer Common on crates.io&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.rs/standardizer-common/latest/standardizer_common/" rel="noopener noreferrer"&gt;Standardizer Common documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/BezotCorp/standardizer/releases" rel="noopener noreferrer"&gt;Releases and downloads&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  About BezotCorp
&lt;/h2&gt;

&lt;p&gt;BezotCorp is an independent software initiative exploring software engineering, artificial intelligence, simulation, video games and experimental technologies.&lt;/p&gt;

&lt;p&gt;Rust is at the heart of many of our projects, alongside open-source technologies and a commitment to building reusable, transparent and maintainable software.&lt;/p&gt;

&lt;p&gt;We believe technology should be something we can understand, shape and experiment with.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Imagine. Create. Experiment.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Discover our projects at &lt;a href="https://bezotcorp.com" rel="noopener noreferrer"&gt;bezotcorp.com&lt;/a&gt; or explore our repositories on &lt;a href="https://github.com/BezotCorp" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;What does your current formatting workflow look like?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Do you prefer dedicated commands for each tool, or would a common interface make your development workflow easier?&lt;/p&gt;

&lt;p&gt;We'd be interested in hearing how other developers approach this challenge.&lt;/p&gt;

</description>
      <category>rust</category>
      <category>opensource</category>
      <category>devtools</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
