-
Notifications
You must be signed in to change notification settings - Fork 95
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
i-bem__dom: dropElemCache is broken? #1037
Comments
Wow, dat fight between @levonet and @tavriaforever. |
Mad robots... |
I can't wait until robots start writing code |
@zxqfox I don't understand why cache key should contain blockName. |
@dfilatov same here, but for now it looks like a bug. |
@zxqfox Sorry, I can't make head or tail of what you have written. Could you explain? |
ping |
@dfilatov текущий dropElemCache работает только без параметров, потому что elem кеширует с названием блока, а первый удаляет без. Зачем там название блока — не знаю, в PR наименьшее кол-во измененного кода, по-хорошему, нужны тесты. |
@dfilatov мы разбирали пр в bem-bl и выяснилось что dropElemCache не работает: bem/bem-bl#634 |
oк, теперь я понял |
i-bem__dom: fix dropElemCache logic (close #1038)
Fixed with #1042 |
Looks like it's broken, because it uses
names + buildModPostfix(modName, modVal)
instead ofthis.__self.buildClass(name, modName, modVal)
that containsblockName
./cc @Yeti-or
The text was updated successfully, but these errors were encountered: