Greg Netsas

...and yes, this is a UX task I believe - so it can go into a bug fix release.

Thanks @argiepiano 🙏🏼 ...if this has happened to you as well, then it makes it something that is possibly not as uncommon as I originally thought. By the sound of...

@argiepiano could you please provide a before/after set of code from that custom module you ported, to be used as a sample in the change record?

Hmm 🤔 ...would the solution then be to add some code in `_field_write_instance()` that intercepts any "unexpected" field-instance-specific values in the root of `$instance`, and moves them under `$instance['settings']`?

...by the way, the docblock for the `_field_write_instance()` function says `Stores an instance record in the field configuration database.`, which seems to have been making sense in D7, as that...

@argiepiano opening an issue here and adding the `needs - change record` label and perhaps the `type - documentation` label should be fine. Otherwise, I guess an issue in https://github.com/backdrop-ops/docs.backdropcms.org/issues,...

> Oh, I just realized I've been reading this entire issue incorrectly. The changes in the merged PR are a great step forward and improve the UX nevertheless. So, :+1:

I just opened #5879. Once that's in, it should be easy to improve these dialogs here with entity autocompletes.

Thanks @jenlampton ...the code looks good 👍 ...there's nothing that can be tested, since what was added is tests 🙂 ...the tests have not failed, so we can count that...

Related: I'm not sure what has changed recently, but I've been often testing PRs with RTL languages by doing the following: - enable Language module - add Arabic, or Hebrew,...