translator | handy tool to translate selected text | Autocomplete library

You may find this GitHub thread insightful. Following it, try using:

You could use global variable to control when it can translate and when it can't do it - ie, paused. And use message /start to set it False, and /end to set it True.

Not tested code - I'm not sure if module runs all in one thread
(multiprocessing would need to keep it in file or database).

Code needs also to check user ID so only admin could do this.

As far as I can understand, it would be beneficial to use useCallback for handleRepairClick to avoid rerenders of

That's right. while wrapping handleRepairClick you will, simply speak, prevent creating a new instance of this function so it will save RepairNotice nested component from redundant rerenders because it relies on this function in props. Another good case for useMemo is when you're rendering a list of items and each relies on the same handler function declared in their parent. Very good useCallback explanation here.

But what about showRepairNotice variable? Should it be wrapped in a useMemo for optimization?

It's just a simple "equation" check which is really cheap from performance side - so there is really no need in useMemo here.

Would it be beneficial to wrap message inside of useMemo?

Yes, it would. Since there are at least 3 actions javascript has to fire upon the message (charAt, toLowerCase, slice) and you don't really want this calculations to fire every time the RepairNotice component gets rerendered.

should useMemo be used unsavedData?

It might be preferable to wrap unsavedData into useMemo if NavConfirmModal will be wrapped in React.Memo or in the case of "heavy calculations". So for the current case - it would not really make a difference. (btw calculating unsavedData could be written just like !!status?.unsavedData to get boolean).

And very good useMemo explanation here.

Solution: I concatenated the strings and reset at the end of the loop because the translations kept stacking:

You were really close to the solution. When providing a value for an optional parameter in returnValueMap, you must use the value itself, not just null.

So instead of

You just need to do a strict search.

See 3rd parameter of array_search.

This is the general function that you are looking for.

I cannot promise it will work because I don't have that plugin available.

The original function you are referencing assumes that a $user object is being passed to it, but I'm not seeing that in your implementation, so I'm just going to assume the current logged in user, if they exist.

I pulled all of the globals that I could find. There's also a bunch of functions that are from the plugin that I can't guarantee will be loaded/available, but you should at least get an error than.

Rename the function as you need to, obviously.

I haven't attempted the Arabic translation part, but you're doing that fine so I guess it's not needed for the solution. Instead, I've just reversed the non-number part of the strings.

That being said, does this do what you need?

Currently it's not available, We have added to Azure metrics feature request to the Translator service and it will be added in the near future.