Block-based editing: selection, drag-and-drop, and actions menu - #11
Closed
jondkinney wants to merge 10 commits into
Closed
Block-based editing: selection, drag-and-drop, and actions menu#11jondkinney wants to merge 10 commits into
jondkinney wants to merge 10 commits into
Conversation
jondkinney
force-pushed
the
block-based-editing
branch
from
March 27, 2026 20:24
00f51ac to
0e7bceb
Compare
Full headwayio-customizations branch including all standalone features. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jondkinney
force-pushed
the
block-based-editing
branch
from
March 27, 2026 20:32
0e7bceb to
a610857
Compare
Fixes gem build failure: yarn install --frozen-lockfile rejects the stale lockfile when building Lexxy from a git source in Gemfile. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Render uses Yarn Classic (v1) globally but the repo's yarn.lock is in Yarn Berry (v4) format. Classic can't read the Berry lockfile and fails with --frozen-lockfile. Dropping the flag lets the build succeed regardless of which Yarn version is installed. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Bundler on hosts with Yarn 1 (e.g. Render) cannot build from source because the repo uses Yarn 4 (Berry). Committing the built assets lets the ext/Rakefile skip the build step entirely. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The previous yarn.lock update was run with Yarn 4 (Berry) which silently rewrote the lockfile from v1 to v8 format. Render has Yarn 1 installed and cannot parse the v4 format. Restore the original Yarn 1 lockfile from headwayio-customizations. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This repo uses Yarn 1 (Classic). The .yarnrc.yml with nodeLinker: node-modules is a Yarn 4/Berry config that causes Yarn 4 to silently rewrite the lockfile when run locally. Removing it prevents accidental lockfile format upgrades. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
With the Yarn 1 lockfile restored and .yarnrc.yml removed, the ext/Rakefile build step works correctly on hosts with Yarn 1. No need to commit 1.1MB of generated JS. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Corepack on GitHub Actions and other hosts auto-downloads the latest Yarn (v4) which cannot read Yarn 1 lockfiles. Adding packageManager field tells Corepack to use Yarn 1.22.22. Pre-built assets are also committed so the ext/Rakefile skips the yarn build step entirely — no dependency on Yarn being installed at all. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The packageManager field in package.json pins Corepack to Yarn 1.22.22, so yarn install + yarn build works correctly on all hosts. No need to commit build artifacts — the ext/Rakefile builds from source when the assets don't exist. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
WebKit/Safari does not support requestIdleCallback. Optional chaining (requestIdleCallback?.()) does not prevent the ReferenceError because it only guards property access on objects, not undeclared variables. Use typeof check instead. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Member
Author
|
Closing in favor of #12 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Note: This PR contains the full
headwayio-customizationsbranch diff, including all standalone features (PRs #4-#10). Once those are refined and merged individually, this PR should be rebased to contain only the block-editing-specific changes.Test plan
🤖 Generated with Claude Code