[sammyapoex]

Follow-up to #2, which was merged at 5b5d68f — three commits on that branch landed after it and are cherry-picked here, plus the release bump.

Changes

• Display STI subclasses through their base class's registration. With flipside_entity in User, an Admin < User record was looked up as "Admin": its entity showed as User #id and display_entity(admin) raised KeyError. The registration is now looked up through the class's ancestors, so a subclass uses the closest registered class and its own registration still wins. (Handle deleted entities #2's fix covered only the subclass-registered case.)
• Verify Flipside.flippables at boot when the app eager loads. Since Handle deleted entities #2 checks the list lazily, an unlisted class using the macros, or a listed class registering nothing, passed boot and CI and failed on the first UI visit. The Railtie now runs the same check in after_initialize when eager_load is on. Rails eager loads before after_initialize in railties 6.1, 7.0 and 8.1 (checked in source). Smoke-tested by booting a minimal Rails 8.1 app against this code: listed → boots; unlisted → Flipside::Error at boot; listed-but-missing → NameError at boot; no eager load → boots. That run also confirmed the deprecator is registered in Rails.application.deprecators.
• README: note that soft deletes running destroy callbacks (e.g. paranoia) also remove a record's entities.
• Bump version to 0.4.0 and date the changelog.

Releasing

bundle exec rake release does not work as-is: rake (and standard) are not in the bundle. Either add them as dev dependencies or release with gem build flipside.gemspec && gem push flipside-0.4.0.gem.

Note for apps upgrading

Apps that raise on deprecations (e.g. config.active_support.deprecation = :raise in test) will fail to boot while they still call register_entity/register_role, since the deprecator now follows the app's settings. Migrate to the macros in the same change as the bump.

Testing

bundle exec rspec — 70 examples, 0 failures.

🤖 Generated with Claude Code