You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a workaround for now, which is to have two CSS files - one for the editor, and one that's includes this config but is excluded in the plugin's configuration.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
First, I'm very happy to make the PR for this one.
In our case, we separately generate a "global" CSS file that includes common utilities for our micro-frontend apps, to prevent duplication.
Each micro-frontend build and deploys its own CSS. They're told to omit that "global", which works well, but the blocklisted classes. Example below:
I have a workaround for now, which is to have two CSS files - one for the editor, and one that's includes this config but is excluded in the plugin's configuration.
Beta Was this translation helpful? Give feedback.
All reactions