{
  "id": 2103180,
  "title": "I shipped a plugin with one branch I hadn't tested — so I built a fallback",
  "url": "https://urgent.news/2026/08/20/i-shipped-a-plugin-with-one-branch-i-hadnt-tested-so-i-built-a",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-20T08:30:58.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/eugeniya_ivanova_4a58eadc/i-shipped-a-plugin-with-one-branch-i-hadnt-tested-so-i-built-a-fallback-lc8"
  },
  "original_language": "en",
  "account": "The wire report covers a developer's experience shipping an Obsidian plugin with an untested branch, leading to a cascade of issues during review. The plugin, built with Claude Code, takes notes and sends them to social accounts on a schedule. However, six changes were required by Obsidian's review guidelines, such as avoiding innerHTML, using createEl for DOM building, and adhering to specific styling and command title conventions. Additionally, network requests needed to go through Obsidian's API on non-desktop devices, and the plugin had to properly handle OAuth login and API key fallback. Finally, the release files needed artifact attestation through GitHub Actions to prove they came from the developer's code.",
  "summary": "I wrote the Obsidian plugin with Claude Code: it typed the code; the rules, reviews, and decisions were mine. I led, argued with it, redid things, and submitted the plugin for review myself. I'm not an engineer. My job is getting people to actually use our product. The plugin itself is simple: one main.js , 557 lines, zero dependencies, Obsidian API only. It takes the note you have open and sends…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}