43081j / 43081j/postcss-styled-components

Exception error detected by stylelint

Abierto
#10 4 comentarios 1 reacción 0 asignados Ver en GitHub
Lenguaje dominante
TypeScript
Estrellas
12
Forks
1
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

Hello, when I use the following stylelint configuration to format styled-components, when I write styled-components in the tsx file, as long as I write the code, the stylelint plugin of vscode will detect an exception and report an error

This is the configuration of stylelint
{
"extends": ["stylelint-config-rational-order", "stylelint-config-standard"],
"plugins": ["stylelint-order"],
"customSyntax": "postcss-styled-components"
}

This is the error message
SyntaxError: Unexpected keyword 'function'. (11:0) at instantiate (E:\GProjects\UI\node_modules\.pnpm\@babel+parser@7.21.2\node_modules\@babel\parser\lib\index.js:64:32) at constructor
![企业微信截图_16784128377413](https://user-images.githubusercontent.com/54523778/224203120-e3517962-549b-48e6-8f53-999d19e20ec0.png)

When I don't use postcss-styled-components, no such error message will appear, but at the same time, I can't format styled-components

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

The issue is about a syntax error when using postcss-styled-components with stylelint in VS Code for styled-components in TSX files. Start by examining the custom syntax plugin's parsing logic, likely in the main source files of the repository. Reproduce the error with the given stylelint configuration and a sample TSX file containing styled-components. Check how the plugin handles the 'function' keyword in the context of styled-components. Look at existing tests to understand expected behavior and add a test case for this scenario.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
typescript
Área
developer-experience, tooling
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
45/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.