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

fix(types): make tailwindFunctions and tailwindAttributes optional #206

Merged
merged 1 commit into from
Aug 22, 2023
Merged

fix(types): make tailwindFunctions and tailwindAttributes optional #206

merged 1 commit into from
Aug 22, 2023

Conversation

giacomoferretti
Copy link
Contributor

Recently stumbled upon this error, which there is already a workaround here: #161 (comment)

It seems that in #162 these optional arguments were made necessary. See more below.

Before

export interface RawOptions {
  tailwindConfig?: string
  tailwindFunctions?: string[]
  tailwindAttributes?: string[]
}

After

export interface PluginOptions {
  /**
   * Path to the Tailwind config file.
   */
  tailwindConfig?: string

  /**
   * List of custom function and tag names that contain classes.
   */
  tailwindFunctions: string[]

  /**
   * List of custom attributes that contain classes.
   */
  tailwindAttributes: string[]
}

@adamwathan
Copy link
Member

Thanks!

@adamwathan adamwathan merged commit 14979f4 into tailwindlabs:main Aug 22, 2023
@giacomoferretti giacomoferretti deleted the fix/optional-plugin-options branch August 24, 2023 07:18
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