Skip to content

Conversation

@jrutila
Copy link
Contributor

@jrutila jrutila commented Mar 12, 2025

πŸ”— Linked issue

#964

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

Tailwindcss does not seem to work with content like this pages/to/[...path].vue. This change will replace those paths with a content like this pages/to/?...path?.vue. The question mark means any character. I tried many ways (like escaping the brackets) but they didn't seem to work.

I didn't write unit tests as the unit test system wasn't clear. Maybe if someone can give me an idea how to do this, I can write the tests.

@netlify
Copy link

netlify bot commented Mar 12, 2025

πŸ‘· Deploy request for nuxt-tailwindcss pending review.

Visit the deploys page to approve it

Name Link
πŸ”¨ Latest commit 270124e

@what-the-diff
Copy link

what-the-diff bot commented Mar 12, 2025

PR Summary

  • Modification to Filename Processing in createInternalContext Function
    The method in which filenames are handled within the createInternalContext function has been updated. The change involves a transformation that replaces any occurrences of [...] with ?...?.... This enhancement aids in dealing with issues that involve glob matching for filenames, effectively resulting in more accurate and efficient file locating and handling tasks.

Copy link
Collaborator

@ineshbose ineshbose left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix ❀️

@ineshbose ineshbose merged commit e308105 into nuxt-modules:main Mar 15, 2025
3 checks passed
@ineshbose
Copy link
Collaborator

Hey @jrutila, forgive me for asking so late - would the provided regex work for [[slug]]?

@jrutila
Copy link
Contributor Author

jrutila commented Apr 8, 2025

Hey @jrutila, forgive me for asking so late - would the provided regex work for [[slug]]?

If I recall correctly, that slug worked before, already. The regex requires there to be a dot in the path to make the replacement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants