# Removal of Ember string prototype extensions

**URL:** <https://meta.discourse.org/t/removal-of-ember-string-prototype-extensions/283513>\
**Category:** Development\
**Created:** [October 25, 2023, 5:06pm UTC](https://meta.discourse.org/t/removal-of-ember-string-prototype-extensions/283513 "2023-10-25T17:06:33Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [October 26, 2023, 10:10am UTC](https://meta.discourse.org/t/removal-of-ember-string-prototype-extensions/283513/4 "2023-10-26T10:10:57Z")

</div>

I had a look through `all-the-themes` and `all-the-plugins`, and there are just a couple of public plugins which need fixing up. I made PRs here: (cc @merefield @angus)

- [Remove use of Ember string prototype extensions by davidtaylorhq · Pull Request #35 · paviliondev/discourse-layouts · GitHub](https://github.com/paviliondev/discourse-layouts/pull/35)

- [Remove use of Ember string prototype extensions by davidtaylorhq · Pull Request #7 · paviliondev/discourse-news · GitHub](https://github.com/paviliondev/discourse-news/pull/7)

Godfrey did some digging for us into why the JQuery commit triggered this, and his findings are in [this PR](https://github.com/discourse/discourse/pull/24101). So, it’s technically possible for us to restore this functionality, but it involves applying a patch to an upstream dependency which is not ideal.

Given the complexity, and that we’d be removing them in a few months anyway, I think it makes sense to just double-down on the removal now. I’ve formalised that in this PR:

[https://github.com/discourse/discourse/pull/24110](https://github.com/discourse/discourse/pull/24110)

Let us know if you have any questions/concerns

---

_[View the full topic](https://meta.discourse.org/t/removal-of-ember-string-prototype-extensions/283513)._
