Polymorphic Association Storage Strategy

This feature thread tracks the development and enhancement of strategies for managing polymorphic associations in Rails, focusing on reducing coupling between the codebase and the database. Initial efforts addressed the challenges of namespace changes breaking polymorphic associations. This post details a solution to stop storing class names as polymorphic types, instead using arbitrary strings. This allows for easier refactoring of class names and namespaces without database migrations. The solution involves overriding the `polymorphic_name` method and adjusting association scopes to handle both old and new `polymorphic_type` values during migration, followed by a cleanup task to remove the old values. The main benefit is reduced coupling between the codebase and the database, allowing for easier class and module renaming without database modifications.