# Override existing Discourse methods in plugins

**URL:** https://meta.discourse.org/t/override-existing-discourse-methods-in-plugins/83389
**Category:** Developers
**Tags:** plugin-guides, how-to
**Created:** [March 20, 2018, 11:37am UTC](https://meta.discourse.org/t/override-existing-discourse-methods-in-plugins/83389 "2018-03-20T11:37:16Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [May 31, 2020, 11:09pm UTC](https://meta.discourse.org/t/override-existing-discourse-methods-in-plugins/83389/5 "2020-05-31T23:09:16Z")

</div>

Yes, indeed. Since that post, updates to Discourse’s use of rails have made `require_dependency` unecessary. I’m unable to edit the post to address that. See further:

> [@Upgrading Discourse to Zeitwerk](https://meta.discourse.org/t/upgrading-discourse-to-zeitwerk/128337):
>
> Rails 6 ships with two autoloading modes: zeitwerk and classic. In that pull request [DEV: Upgrading Discourse to Rails 6 by KrisKotlarek · Pull Request #8083 · discourse/discourse · GitHub](https://github.com/discourse/discourse/pull/8083) I upgraded Rails to version 6.0.0 with classic autoloader as a transitional phase. It would be interesting to try to switch to Zeitwerk. Zeitwerk is an efficient and thread-safe code loader for Ruby. As long as the project is following naming conventions, Zeitwerk can find correct files and load them on deman…

---

_[View the full topic](https://meta.discourse.org/t/override-existing-discourse-methods-in-plugins/83389)._