mbeditor 0.12.0 → 0.12.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c8e586fb734529e92147e9fb6935782e79baeb9722c833e8df0a97cc2c86c637
-  data.tar.gz: 5da9242367bd195c715af433c8fb12fa440a610cacb5a1ff871cb8361c82233a
+  metadata.gz: b6645751ebceaf2b9754d5aabb417549334518db35027e1bd6c08d9fede2d7a5
+  data.tar.gz: edb2a8a2696f5aac16fcdcd4bbbf728f5d05a7af14ffca326a59ec7c0d40b860
 SHA512:
-  metadata.gz: f403b63083bc139fc6546477c42fb476283213f0409a287ec3ffe46cc1a90cb10f197d6521216efce8121d910fdb8b2c94eefd8cd0abd8829725c852f043e57a
-  data.tar.gz: 219a64ac7ecf5e2ded2081058f64f0bb4b0ce8373eac4f3cdcd8f9ca87aacd887676e680c31f360848dbcc255cfcdd176eaf67389569c64143639bf2643538f6
+  metadata.gz: 5f9d7559b69d80a1d8d9d094d5513a69048ce62ea385630ca59811e0dafd50ca65afa988e1f560cc32d78fc7b71dceedb78b30f1ba190e00b465d1026e3554d5
+  data.tar.gz: a8a3de31439ff3a937db30a04dbfd631694f50ccbcce4c3fb3571dfa66cd798cf8df29b45855467a9ff783a919893829472b241523d7230468944a3accad04f9

data/CHANGELOG.md

@@ -7,6 +7,68 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.12.1] - 2026-08-03
+
+### Added
+- **The collaboration name now comes from the signed-in user automatically.**
+  Previously it required a `user_name_callback`; with none set the editor fell
+  straight through to a generated name like "Witty Operator" even on an
+  authenticated instance. When no callback is configured, the name is now read
+  off `current_user`, trying `name`, `full_name`, `display_name`, `username`,
+  `login` and `email` in order. New `config.user_name_methods` names your own
+  column instead — `%w[preferred_name]` — so the common case no longer needs a
+  callback at all. An explicit `user_name_callback` still wins.
+
+  This works when your auth library exposes `current_user` to an
+  `ActionController::Base` subclass, which Devise and Sorcery do. A
+  `current_user` written by hand on your own `ApplicationController` is **not**
+  reachable — the engine's controllers do not inherit from it — so that case
+  still needs a callback reading `session` directly.
+
+### Changed
+- **The model graph is laid out by dependency, not by traversal order.** It now
+  uses the Sugiyama layered method — break cycles, layer by longest path, cut
+  crossings with the median heuristic, then straighten — which is what Graphviz
+  `dot`, and so Rails ERD, uses for this picture. The previous radial layout
+  became one enormous circle on a real schema, fitted so far out that no box was
+  legible. A model's position now tells you something: depth reads left to
+  right, and each connected part of the schema is drawn as its own area.
+
+- **Your own presence chip only appears once someone else is connected.** Action
+  Cable is up in any normal dev setup, so it used to sit in the toolbar
+  permanently announcing a session of one.
+
+### Fixed
+- **The model graph was unusable on a large schema.** On 300 models and 513
+  associations a single zoom tick cost 27 ms; it is now 0.2 ms. Three causes,
+  all compounding: the entire layout ran on every render, the pan/zoom transform
+  sat in the render output so each tick rebuilt ~7,000 SVG elements, and the
+  wheel handler read `getBoundingClientRect()` per tick, forcing a synchronous
+  reflow of the whole scene.
+- **Fit-to-pane produced a zoom the controls refused to honour.** It clamped to
+  `min(1, ...)` but not to the minimum zoom, so a large graph fitted at ~0.04
+  against a 0.2 floor — and the first scroll snapped up to the floor, a fivefold
+  jump anchored on the cursor that looked like the diagram leaping somewhere
+  random. The floor is now low enough to frame a few hundred models, and the fit
+  clamps to the same range the wheel enforces. Opening the tab also no longer
+  leaves the graph unfitted when the pane has not been sized yet.
+- **Hovering a model now shows what its associations actually are** — macro,
+  name, direction and `through:` — and dims every unrelated edge, which is the
+  only way to follow one model's relationships among hundreds of lines.
+- **Clicking a model zooms to it** instead of opening its schema; the schema is
+  an explicit button in the model's header, so navigating no longer throws a
+  modal at you.
+- **The model-graph search field drew its text over a magnifier icon.** The icon
+  comes from the vendored Pico stylesheet, whose selector outranks a plain class
+  rule — disabling the browser's own `type="search"` decorations did not touch
+  it.
+- **A failing `user_name_callback` was swallowed silently.** Any exception
+  returned a bare `nil`, which made a broken callback indistinguishable from an
+  unconfigured one: you got the generated name and no clue why. The usual cause
+  is a `NameError` on a `current_user` the engine cannot see. It is now logged
+  as `[mbeditor] user name lookup failed: ...` and still never breaks the
+  request.
+
 ## [0.12.0] - 2026-07-31
 
 ### Added
@@ -50,9 +112,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - **A model graph — an entity diagram of the host app's ActiveRecord models.**
   The activity-bar button opens it as a full-width editor tab, drawing each
-  model with its fields and laying them out radially around whichever model has
-  the most associations. Search centres the view on a model; hovering an edge
-  names the relation.
+  model with its fields. Search centres the view on a model; hovering an edge
+  names the relation. (Released with a radial layout; replaced by a layered one
+  in the next version — see Unreleased.)
 
   Associations are read by **reflection, not by parsing model files**. mbeditor
   runs inside the host app, so `reflect_on_all_associations` is right there and

data/README.md

@@ -162,7 +162,8 @@ See [Resilient Routing](#resilient-routing) for details.
 
 | Option | Default | Description |
 |--------|---------|-------------|
-| `user_name_callback` | `nil` | Proc resolving the display name shown on your caret during realtime collaboration. Executed via `instance_exec` inside the controller (like `authenticate_with`), so it can read `session`, `cookies`, `current_user`, etc. — e.g. `proc { current_user&.name }`. When `nil` or it returns a blank value, each browser falls back to a generated, locally-persisted, user-editable name. Collaboration activates once another participant actually connects, not merely when Action Cable is up (see [Collaborative pairing](#collaborative-pairing-optional)). |
+| `user_name_callback` | `nil` | Proc resolving the display name shown on your caret during realtime collaboration. Only needed when the automatic lookup can't reach your user — see `user_name_methods` below. Executed via `instance_exec` inside the engine's controller (like `authenticate_with`), so it can read `session`, `cookies`, `params`, and anything your auth library exposes to an `ActionController::Base` subclass — e.g. `proc { User.find_by(id: session[:user_id])&.name }`. **It cannot see helper methods defined on your own `ApplicationController`**, because the engine's controllers do not inherit from it; a hand-rolled `current_user` living there will raise `NameError`, which is logged as `[mbeditor] user name lookup failed` and falls back to the generated name. |
+| `user_name_methods` | `%w[name full_name display_name username login email]` | Attributes tried on `current_user`, in order, when no `user_name_callback` is set — the first non-blank one becomes your collaboration display name. This is what makes an authenticated editor show real names with no extra wiring, provided your auth library exposes `current_user` to `ActionController::Base` (Devise and Sorcery do; a `current_user` you wrote yourself on `ApplicationController` does not). Set it to your own column instead of writing a callback, e.g. `%w[preferred_name]`. |
 
 ## JavaScript intelligence
 
@@ -376,6 +377,42 @@ common cause of *"the other person's edits never show up."* For pairing, run a s
 worker (`WEB_CONCURRENCY=0`, or `bundle exec rails server` which is single-process by
 default). A multi-worker setup would additionally need a cross-process cable adapter, but
 the in-memory buffer still would not be shared — single-process is the supported mode.
+
+#### Showing real usernames
+
+Each participant's caret and presence chip are labelled. With no configuration
+the label is a generated name like *Witty Operator*, persisted per browser and
+editable by clicking your own chip.
+
+**If your auth library exposes `current_user` to controllers** — Devise and
+Sorcery both do, because they include their helpers into `ActionController::Base`
+— it already works with no configuration at all. mbeditor reads the first
+non-blank of `name`, `full_name`, `display_name`, `username`, `login`, `email`.
+
+To point it at a different column:
+
+```ruby
+Mbeditor.configure do |c|
+  c.user_name_methods = %w[preferred_name email]
+end
+```
+
+**If `current_user` is your own method on `ApplicationController`**, mbeditor
+cannot see it — the engine's controllers inherit from `ActionController::Base`,
+not from your `ApplicationController`. Resolve the user yourself instead; the
+proc runs in the engine's controller, so `session`, `cookies` and `params` are
+all available:
+
+```ruby
+Mbeditor.configure do |c|
+  c.user_name_callback = proc { User.find_by(id: session[:user_id])&.name }
+end
+```
+
+An explicit `user_name_callback` always wins over the automatic lookup. If it
+raises or returns blank you get the generated name, and the reason is logged as
+`[mbeditor] user name lookup failed: …` rather than silently swallowed.
+
 ## Search performance
 
 Project search and JS definition lookups pick a backend per call:

data/app/assets/javascripts/mbeditor/components/MbeditorApp.js

@@ -4217,7 +4217,12 @@ var MbeditorApp = function MbeditorApp() {
             !toolbarIconOnly && " Git"
           )
         ),
-        collabEnabled && collabIdentity && React.createElement(
+        // Your own chip appears only once someone else is actually connected.
+        // Alone it told you nothing — Action Cable is up in any normal dev setup,
+        // so it sat in the toolbar permanently announcing a session of one. While
+        // pairing it earns its place: it is how your peers see you, and it is the
+        // control for renaming yourself.
+        collabEnabled && collabIdentity && collabPeerIds.length > 0 && React.createElement(
           React.Fragment,
           null,
           React.createElement("div", { className: "statusbar-sep" }),