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

[Feature]: Allow pass in component prefix #942

Closed
RayGuo-ergou opened this issue Oct 10, 2024 · 2 comments · Fixed by #943
Closed

[Feature]: Allow pass in component prefix #942

RayGuo-ergou opened this issue Oct 10, 2024 · 2 comments · Fixed by #943
Assignees

Comments

@RayGuo-ergou
Copy link
Contributor

RayGuo-ergou commented Oct 10, 2024

Description

In

/(?<=<(x-|livewire:)[^<]*?\s):{1,2}(?<!=>)[\w\-_.]*?=(["'])(?!=>)[^\2]*?\2(?=[^>]*?\/*?>)/gim,

It checks prefix (x-|livewire:). However, when I use a new library flux the component name is <flux:xxx>.

The issue:

Currently it formats

:key="$foo->bar"

to

:key="$foo - > bar"

Suggested Solution

Can we support this or even future to apply user pass in the prefix.

can be default as ['x-', 'livewire:'] so in the future in another lib defines it own component name, this formatter still supports it.

Alternatives

No response

Additional Context

No response

Copy link
Contributor

github-actions bot commented Dec 9, 2024

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot added the Stale label Dec 9, 2024
@RayGuo-ergou
Copy link
Contributor Author

Not stale.

@github-actions github-actions bot removed the Stale label Dec 10, 2024
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 a pull request may close this issue.

2 participants