Skip to content
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

[bug] word-break properties do not work #103

Closed
jbs-marcus opened this issue May 29, 2024 · 0 comments · Fixed by #104
Closed

[bug] word-break properties do not work #103

jbs-marcus opened this issue May 29, 2024 · 0 comments · Fixed by #104
Assignees
Labels
bug Something isn't working

Comments

@jbs-marcus
Copy link
Contributor

Describe the bug
There is no way to use break-normal, break-words, break-all, and break-keep.

Expected behavior
That the project builds successfully.

Actual behavior
Build fails with:

error TS2353: Object literal may only specify known properties, and 'wordBreak' does not exist in type 'WindTypes'.

27         wordBreak: "break-words",
           ~~~~~~~~~

  node_modules/tailwindest/dist/index.d.ts:198:9
    198         base?: StyleType;
                ~~~~
    The expected type comes from property 'base' which is declared here on type '{ truthy: WindTypes; falsy: WindTypes; base?: WindTypes | undefined; }'

Additional context
After a quick search, the code to make this work already exists, but is not referenced in the code base. A pull request with a fix will be submitted soon.

  • Fedora Linux 40 (KDE Plasma) x86_64
  • tailwindest 2.3.0
  • tailwindcss 3.4.3
  • react 18.3.1
  • vite 4.5.3
  • typescript 5.4.5
@jbs-marcus jbs-marcus added the bug Something isn't working label May 29, 2024
jbs-marcus added a commit to jbs-marcus/tailwindest that referenced this issue May 29, 2024
Adds missing import and extend of TailwindWordBreakType
@danpacho danpacho linked a pull request May 30, 2024 that will close this issue
11 tasks
danpacho added a commit that referenced this issue May 30, 2024
🐛 add missing word break properties (fixes #103)
@danpacho danpacho linked a pull request Jun 27, 2024 that will close this issue
11 tasks
@danpacho danpacho removed a link to a pull request Jun 27, 2024
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants