Skip to content
Snippets Groups Projects

Follow-up from "Properly implement prepending for Concern"

    • Open Issue created by Lin Jen-Shin @godfat

    The following discussion from gitlab-ee!7079 should be addressed:

    My consideration:

    • This should make ActiveSupport::Concern less confusing with prepend, so if people really want to use it, then I think this is a good fix.
    • I never liked ActiveSupport::Concern and adding more stuffs to it will make people couple with it even deeper. (there is no changes between activesupport v4.2.10 and v5.2.1)
    • I don't know how upstream will think about this, and I won't enjoy convincing them.
    • This might not work with older Rubies. Last time I fixed something in rspec-mocks, but I broke Ruby 1.8.7 and they seem still want to maintain it.
    0 of 1 checklist item completed

    Designs

      Child items ...