Comments (15)
I know, I'm a little bit late to the party. But in case someone is interested in this. You can suppress the backticks with prose-code:before:hidden prose-code:after:hidden
from tailwindcss-typography.
This did not work for me (TW2.0) - when I was adding this to my tailwind config, it completely broke all styles.
I had to add a small change, and it worked
// tailwind.config.js
module.exports = {
theme: {
extend: {
typography: {
DEFAULT: {
css: {
'code::before': {
content: '""'
},
'code::after': {
content: '""'
}
}
}
},
},
},
plugins: [require("@tailwindcss/typography")],
};
from tailwindcss-typography.
Apologies, I made a mistake in the tailwind.config.js
. This is working for me now:
// tailwind.config.js
module.exports = {
theme: {
typography: {
default: {
css: {
'code::before': {
content: '""',
},
'code::after': {
content: '""',
},
},
},
},
},
plugins: [require("@tailwindcss/typography")],
};
from tailwindcss-typography.
Actually I know exactly what is happening now, sorry.
Your changes are being merged with our existing code
key, which comes before our code::before
and code::after
keys.
Here's our code:
code: {
color: defaultTheme.colors.gray[900],
fontWeight: '600',
},
'code::before': {
content: '"`"',
},
'code::after': {
content: '"`"',
},
When you're code is merged in, it creates this object:
code: {
color: defaultTheme.colors.gray[900],
fontWeight: '600',
'&::before': {
content: '""',
},
'&::after': {
content: '""',
},
},
'code::before': {
content: '"`"',
},
'code::after': {
content: '"`"',
},
So when it's all flattened out, our existing code::before
and code::after
selectors win. This is sort of a tough one to figure out how to "fix" because the current behavior is actually really useful for lots of situations, so we might just want to figure out a way to let the user control this more finely.
Going to close this for now since there's a solution (use our keys) and I can't say for sure we are going to take action on it.
from tailwindcss-typography.
@adamwathan some findings... Writing in this way will correctly overwrite the original style. Seems like using &::before, &::after
will cause the styles to be applied before the original styles.
// tailwind.config.js
module.exports = {
theme: {
typography: {
default: {
css: {
'code::before': {
content: '""',
},
'code::after': {
content: '""',
}
// ...
},
},
},
},
plugins: [
require('@tailwindcss/typography'),
// ...
],
}
from tailwindcss-typography.
@Waterdrips ☝️ this should do the trick?
from tailwindcss-typography.
For v3, this works for me.
from tailwindcss-typography.
Can you create a GitHub repo that reproduces this? I just tried it on our blog and was able to override it no problem with your exact code.
from tailwindcss-typography.
Hi @dpyzo0o, if you add !important
it should work. So like this:
typography: {
default: {
css: {
code: {
'&::before': {
content: '"" !important',
},
'&::after': {
content: '"" !important',
},
}
// ...
},
},
},
I was able to reproduce your issue though, I think the problem is that the new class gets added before the typography plugin class and thus overwriting it.
I imagine this is something that could be fixed?
from tailwindcss-typography.
@vincentdoerig Yes, adding !important
can solve the issue but I'm trying to avoid using !important
if possible. Indeed I'm able to remove the backquotes by setting display: none
// tailwind.config.js
module.exports = {
theme: {
typography: {
default: {
css: {
code: {
'&::before': {
display: 'none',
},
'&::after': {
display: 'none',
},
}
// ...
},
},
},
},
plugins: [
require('@tailwindcss/typography'),
// ...
],
}
@adamwathan I'm sure this issue is reproducible, here is a minimal repo that reproduces the issue, https://github.com/dpyzo0o/tailwindcss-bug-reproduce
from tailwindcss-typography.
Ah yeah you know what I think I wrote it that way when I was testing things out, so I was wrong when I said I used your code exactly 🤦
It looks like this is due to a particular detail of how deep merging works in lodash, which causes object properties to be merged in a different order than I'd expect (overrides are added as earlier keys in the object being merged to, not later).
For now I would recommend mimicking the exact selector we use in the styles.js
reference whenever you need to make an override, and we will see about making the merging behavior more intuitive.
EDIT: Actually doesn't seem like a lodash issue, not sure where this order issue pops up, might be in postcss-js. Will explore.
from tailwindcss-typography.
Hello, we have the same problem in that all our inline code is showing backticks, which we don't want. You mentioned that you have a solution: use our keys. Please can you explain this? I've gone through all the above and we still see backticks everywhere.
from tailwindcss-typography.
I know, I'm a little bit late to the party. But in case someone is interested in this. You can suppress the backticks with
prose-code:before:hidden prose-code:after:hidden
But not too late! Thanks!
from tailwindcss-typography.
I know, I'm a little bit late to the party. But in case someone is interested in this. You can suppress the backticks with
prose-code:before:hidden prose-code:after:hidden
This did the trick! Thank you!
from tailwindcss-typography.
prose-code:before:hidden prose-code:after:hidden
This worked! Thank you so much!!!!
from tailwindcss-typography.
Related Issues (20)
- Generated classes do not respect base tailwind.config "important" setting HOT 2
- `not-prose` does not reset `prose-lg` HOT 2
- Bottom margin is not reset for last child when redefined in lg prose HOT 2
- Wrong order of custom utilities and prose with variant HOT 3
- 0.5.10 causes '[class~=not-prose] *)):before' is not a valid selector HOT 5
- Peer dependency invalid version requirement HOT 1
- `prose-code` targets both inline and block code HOT 5
- Bad DX: [object Object] appearing in CSS when customizing typography
- Unable to change video size using prose-video:{utility} HOT 3
- Does not work on wechat webview HOT 1
- Numbered lists are being cut off HOT 1
- Markdown Rendered Graphs Overflows the Screen HOT 1
- Type error in the config: Binding element 'theme' implicitly has an 'any' type. HOT 1
- Links don't have a default hover state HOT 3
- Prose not formatting markdown tables correctly HOT 1
- The rendered image height is incorrect. HOT 1
- headings modifier does not work HOT 5
- Prose class adds inner border to specific font on Chrome HOT 2
- Different rendering on Firefox HOT 3
- @apply prose is failing the first- and last-child selectors HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tailwindcss-typography.