pcbowers / alpine-intellisense Goto Github PK

View Code? Open in Web Editor NEW

19.0 19.0 1.0 3.29 MB

IntelliSense for Alpine.js

Home Page: https://marketplace.visualstudio.com/items?itemName=pcbowers.alpine-intellisense

License: MIT License

TypeScript 100.00%

alpine-intellisense's Introduction

Hi 👋, I'm Chris Bowers

Want to reach out? Connect with me at [email protected]!

alpine-intellisense's People

Contributors

Stargazers

Watchers

Forkers

ivanjeremic

alpine-intellisense's Issues

The extension doesn't respect workspace settings, only user's

I'm working with VSC a DevContainer and I usually rely on settings that are put in [./.vscode/settings.json] within the project's directory, which is read as "overriding", "workspace" settings that should have priority over user settings as far as my understanding goes... (gasp)

So, no, the extension doesn't respect those!

When I apply:

"alpine-intellisense.settings.languageScopes": "blade",

It only works if it's in my personal [settings.json]. And when it's deleted from it and added to the workspace's, the extension defaults back to only supporting html instead.

Quotes within a PHP tag aren't ignored

Quotes within a PHP tag aren't ignored as they should be. This causes syntax highlighting to break.

Here's an example of an inline PHP tag within a <script> tag with proper JavaScript syntax highlighting:

Here's the same example using this plugin:

The syntax highlighting is broken after encountering the first ' inside of the PHP statement as it thinks it's a matching quote. If I swap single or double quote on the attribute it has the same issue.

Blade syntax conflict

When using [Laravel Blade Snippets] extension, which provides syntax highlighting for Blade files that could contain Alpine.js code, the syntax highlighting for Alpine.js code works flawlessly; except for overriding Laravel's Blade directives highlighting, where it makes them pure white!

Here is the look with Laravel Blade Snippets extension alone:

And here is how it looks with your extension along (both altogether):

[Feature] Limit intellisense within the classes

Greetings,

Does the extension work so that its intellisense is limited to html tags? If I press ctrl+space outside html tags, I still get all of the alpine directives and stuff.

Thanks.

highlighting tailwind class directives

First, I"m happy with seeing highlighting instead of a single color, so thank you for your work!

It's fairly obvious why the below happens, but just pointing it out.

Possible to limit parsing to x-*= @data-name= :data-name= maybe?

I have a feeling the x- directive is being removed in future Alpine releases however.

Inspiration for personal project

Hello and first of all thanks for this good extension, sorry for asking here in the issues but there is no discussion tab.

I want to extend .html too for a non alpinejs related project what I noticed when writing events with this extension there is not really an autocomplete for the javascript code written in the script tag, for example

<body>
    <script>
      function clickHandler() {
        console.log("boo");
      }
    </script>

    // the alpine click gives no autocomplete
    <div x-on:click="clickHandler()">Here</div>

    //the native onclick gives autocomplete for clickHandler
    <div onclick="clickHandler()">Here</div>
</body>

Is this supposed to work that way and if not is it possible to tell an custom attribute that everything between "..." should be javascript?

Again sorry for asking here but I'm currently really interested in solving this for me without creating a whole new language. Thanks

Ignores Astro files regardless

I've set astro in the preferences, but it still fails to syntax highlight Alpine within .astro files.

Issue with intellisense in 'regular' text.

I'm seeing the extension be a bit aggressive in terms of suggestions when typing. So for example, on a page w/ no JS at all, I typed:

<p>
Hello world.
</p>

When I typed the period at the end, I got:

As I'm a fast typer, I ened up with: Hello world.alt.

Any reason why it is prompting for stuff with just a period?

[Bug]: highlighting string with // syntax as comments

software version

Alpine Js : 3.13.3
Extension : 1.0.2

here the screen capture:

current workaround / temporary fix is to use the Sperovita/alpinejs-syntax-highlight and disabling this extension grammar via the package.json as this extension is overrode the Sperovita's syntax highlighting.

Here is how you could disable this grammar :

Locate the extension directory on your disc. On Windows, for instance, you'll find it in %USERPROFILE%/.vscode/extensions/pcbowers.alpine-intellisense-1.0.2
Edit the package.json file in that directory.
Locate & delete the grammars

"contributes": {
		"configuration": {
			"title": "Alpine.js IntelliSense",
			"properties": {
				"alpine-intellisense.settings.languageScopes": {
					"type": "string",
					"markdownDescription": "Defines the language scopes for which the snippets will be available.\nUse comma separated values. For example: `html,php,twig,nunjucks`.\nDefault is `html`.",
					"default": "html"
				}
			}
		},
               vvv START DELETE LINE vvv
		"grammars": [
			{
				"scopeName": "alpine-intellisense.injection",
				"path": "./syntaxes/alpine-intellisense.injection.json",
				"injectTo": [
					"text.html"
					],
				"embeddedLanguages": {
					"source.js": "javascript"
				}
			}
		],
               ^^^ END DELETE LINE ^^^
		"html": {
			"customData": [
				"./syntaxes/html.html-data.json"
			]
		},
		"snippets": [
			{
				"path": "./snippets/snippets.code-snippets"
			}
		]
	},

Save the file, close and re-open VS Code (it may warn you on startup that the extension was changed on disc and to reload again; click Ok in the notification and do so).
Viola you can keep using this extension and use the syntax highlighting from Sperovita/alpinejs-syntax-highlight extension.

Upload the extension on Open VSX

Hey there,

Would you kindly make the extension available on VSX, so we can download it in VSCodium?

Thanks.

Extension wrong highlighting valid syntax as errors

(1) alpinejs version: 3.x
(2) Extension version: 1.0.2

The extension is highlighting valid syntax as errors. See screencap below:

The documentation feature only works for HTML files

Greetings, and thank kindly you for the amazing extension.

I noticed that the documentation feature, which I consider to be the best out of the extension's, doesn't work for any other file types, even when defined using the extension setting.

Is there any easy solution to make that documentation popup shows up for Blade files, after setting it using the following code?

"alpine-intellisense.settings.languageScopes": "blade",

Install error

Extension breaks highlighting within some cases in php

Here what I have with extension ON:

And when extension is OFF, highlighting works normally:

[Feature Request:] Support for attributes that are created via helper functions in php

Hi there!

first of all: Amazing work on this package! Reading the regexes makes my brain hurt 😄

I'm having a use case where I don't know how common it is. I construct my html attributes via a helper function attr(), where each attribute is in 'key' => 'value' form. alpine-intellisense picks some attributes up, others don't work. Here's an example:

Would you guys be interested in adding support for this kind of syntax?