moderator | Discord moderator bot for the Discohook support server | Bot library

I was trying to produce a regression plot with the regplot() in the metafor package, fitting a continuous predictor as a restricted cubic spline through the use of the rms package in R, in the context of a multivariable regression.

However, after carefully reviewing all the examples listed here: https://wviechtb.github.io/metafor/reference/regplot.html, I was unable to reproduce the plot desired (i.e., the regression plot of the continuous predictor modelled as a restricted cubic spline).

Here is a reproducible example:

So hey Stackoverflow community, Im here kinda confused on why this stopped working all of the sudden, and I get the error that is stated in the title.

Basically it would check to see if the user who was attempting to mute a user had a higher role than the other user, and if they did.. it would mute them, and if they didn't it would throw an error.

But now all it does is just throw the error stated in the title once again and I cannot find a fix on the docs?

Also when i remove the highest.position from the check, it allows anyone with the right perms to mute anyone above or below them.

So here I am, asking nicely for some help/understanding on why this method of muting users has stopped working unexpectedly.

So, fundamentally, this question is Not opinion-based. I seriously pursuit this issue objectively without feeling mostly arisen from the predominant opinion - Why is extending native objects a bad practice?

and this quesion is related but unanswered questions:

If Object.prototype is extended with Symbol property, is it possible to break code without specifically designed APIs to access Symbol in JavaScript?

Should the extension of built-in Javascript prototypes through symbols also be avoided?

The first question is already closed as they say it's opinion based, and as you might know in this community once a question is Banned, however we modified it, moderators will never bother to re-open. That is the way how the things work here.

For the second question. For some unknown reason, the question has been taken more seriously and not considered as opinion based although the context is identical.

There are two parts to the "don't modify something you don't own" rule:

1. You can cause name collisions and you can break their code.

   By touching something you don't own, you may accidentally overwrite something used by some other library. This will break their code in unexpected ways.

2. You can create tight dependencies and they can break your code.

   By binding your code so tightly to some other object, if they make some significant change (like removing or renaming the class, for example), your code might suddenly break.

Using symbols will avoid #1, but you still run into #2. Tight dependencies between classes like that are generally discouraged. If the other class is ever frozen, your code will still break. The answers on this question still apply, just for slightly different reasons.

Also, I've read opinions(how can we discuss such a thing here without "opinion" base?), they claim

a) Library code Using Symbols exists and they may tweak Symbol API (such as Object.getOwnPropertySymbols())

b) extending object property with Symbol is not different from non-Symbol property fundamentally.

Here, for the major rationale of untouching Object.prototype is due to #1, almost all answers I saw claimed that and we don't have to discuss if there is no Symbol usage.

However, Using symbols will avoid #1 as they say. So most of the traditional wisdom won't apply anymore.

Then, as #2 says,

By binding your code so tightly to some other object, if they make some significant change (like removing or renaming the class, for example), your code might suddenly break.

well, in principle, any fundamental API version upgrade will break any code. The well-known fact is nothing to do with this specific question. #2 did not answer the question.

Only considerable part is Object.freeze(Object.prototype) can be the remaining problem. However, this is essentially the same manner to upgrade the basic API by some other unexpectedly.

As the API users not as API providers, the expected API of Object.prototype is not frozen.

If some other guys touch the basic API and modifies it as frozen, it is he/she who broke the code. They upgraded the basic API without notice.

For instance, in Haskell, there are many language extensions. Probably they solve the collision issue well, and most importantly, they won't "freeze" the basic API because freezing the basic API would brake their eco.

Therefore, I observe that Object.freeze(Object.prototype) is the anti-pattern. It cannot be justified as a matter of course to prevent Object.prototype extension with Symbols.

So here is my question. Although I observe this way, is it safe to say:

In case of that Object.freeze(Object.prototype) is not performed, which is the anti-pattern and detectable, it is safe to perform extending Object.prototype with Symbols?

If you don't think so, please provide a concrete example.

I'm using Chrome v99 and a pretty basic usage of break-inside: avoid - but it does nothing.

Moderator: This is not a duplicate of this post and the 1 answer there isn't helpful.

My objective is to disallow the contents of all these divs from splitting at page breaks:

I am trying to update my Navbar component so that when a user logs in, the navbar dropdown item "Login" changes to "Logout" but I am having issues. I am new to react and JS but learning as I go, so I apologize for any confusion in this question. I have jsx components for my Navbar, Dropdown, Footer, and for each page that a user wants to view which is rendered in my App.js file.

Navbar.jsx:

When the user goes to the url for "/films/:title" it displays MovieDetailContainer which is the component for the path above it and doesnt display its own component. When I flip around the order of the urls the reverse happens. Why is this? I assume its a nesting error but I cant seem to figure it out.

here is code for the routes and the code for the full App/js is below just incase.

So I created this function to apply to a bunch of dataframes that I have inside a dictionary. The thing is, when it comes to the elif part he only does the first statement that he reads.

So for example if I don't have the column 'claimant moderated resultaction' he will create it as I tell him to do but he won't create the 'claimant moderated resultselectedPolicyTitle' because it comes next in the iteration. Same logic for the rest of columns.

UPDATE
i found this solution

...

What I Want:

I am trying to make it so when a member is added or removed from staff in my discord it will update it on the website I have. I've tried doing this with node.js, but then I can't use document attributes and etc. Basically I am wondering if this is possible.

Code JS: