Important strategy with a target

Open
#1 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, tailwindcss
Domain
frontend

Research direction

Start by reproducing the config with '#app' in the 'important' property and compare the generated utility output with Tailwind's documented important modifier. Check whether the plugin or Tailwind version still supports this behavior; done means establishing the expected result and either restoring support or clearly documenting that it was removed.

Written by the indexing model from the issue text.

Description

I added '#app' to the config's 'important' property but it doesn't seem to generate #app .p-4 for example.

It's also possible tw4 removed this feature entirely
https://tailwindcss.com/docs/styling-with-utility-classes#using-the-important-modifier

Do you have any insights on this?

I'm sure

@import "tailwindcss" important;

Will work

Dominant language
JavaScript
Stars
21
Forks
2
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Semantic-Org/tailwindcss-iso

All issues in Semantic-Org/tailwindcss-iso

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.