-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different
class names are but Same
obfuscated name
#18
Comments
A new issue was created. |
Hi @soranoo, just because I'm too lazy to create a new issue, I'm commenting on the old bug here. I think it's very rare that this happens, but is there any way to be sure it doesn't overlap anymore? Package version I just hope this patch won't change the class name again, because it seems like you'll be editing the My
|
It is not necessary to comment on both issues. It is redundant. Any issue with random generation may related to the underlay random generation algo if a new algo is introduced the rng behaviour will be changed and a new class name will be generated. If you want to keep the old class name for some reason, you can simply modify the JSON manually. |
Sounds cool! Have you had time to push it to npm yet, or is there still work to be done? I still think it's a good idea that you can have it check if there is a duplicate class in However, I still wonder if I'm that unlucky, in possible cases, I have 2 overlapping classes... or is it called luck? |
I found I forgot to pull it Sorry about that. Do you mean the collision before the update? |
Yes, in |
You have to use |
omg when did I remove the |
If it is no dulipcation report after 24hrs I will close this issue. But plz feel free to comment here if it happened again. |
It seems like this bug needs to wait until someone "lucky" encounters the same situation as I mentioned above to be sure it works haha |
Bruhh, I understand how you feel when you comment on the No need to wait anymore, I'm the "lucky" one 🤣 |
Yes, exactly. So I try my best to give response in any format to let the issue raiser know "someone" is care about it. |
Version:
v2.2.2 released
As the title:
I tried it twice so I think this is not a
1% random
error case (cuz I don't know if this plugin supports making sure the class names won't overlap)The
.xjun0e
class (aka.pr-[1.41dvw]
) should be in<main>
tag ✅:Below, right where
.side-box-line
should be, there should be anotherobfuscated class name
. But it has the same name as.pr-[1.41dvw]
⛔:Note:
.side-box-line
is just a className, no direct styles were applied to it, it only gets styles through class like this[&_.side-box-line]:left-0
and this class is also not in<main>
(I explain like this to avoid misunderstanding)That causes
.side-box-line
, which should look like this ✅:to look like this ⛔:
The green color is the
padding-right
effect:The text was updated successfully, but these errors were encountered: