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

html intellisense #101

Open
sacesare opened this issue Jul 10, 2022 · 3 comments
Open

html intellisense #101

sacesare opened this issue Jul 10, 2022 · 3 comments

Comments

@sacesare
Copy link

Auto completion is not working for html tags. It would be useful to integrate standard html/css suggestion module.
Thanks.

@pgfearo
Copy link
Member

pgfearo commented Jul 25, 2022

As there's no specific support for HTML or CSS in the XSLT language specification (HTML is of course in the XSLT serialisation specification though) this feature is not a good fit for this specific project so I can't add this feature at the moment I'm afraid.

@sacesare
Copy link
Author

I understand, that xslt can generate not only html but any text content, but support for standard schemas/vocabularies would be very useful addition. Beside of that, vscode already have extensive support for html/css/javascript, not talking about visual studio brilliant mixed xslt/html support, several vscode extensions have mixed/notebook code style support too.

@pgfearo
Copy link
Member

pgfearo commented Jul 31, 2022

I've just researched the Oxygen XML editor's does for HTML intellisense. It's support is more basic than I had assumed and therefore easier to implement: it doesn't track both the XSLT and HTML trees at the same time. While it considers HTML parent elements at the cursor-position to limit the auto-complete list, it resets the HTML context for each XSLT sequence constructor. This isn't what I've done for previous XSLT editors (e.g. XMLQuire) but probably meets the 'good enough' threshold for most users.

Oxygen XML allows a user setting or project setting to control what XML vocabulary, if any, is supported in the XSLT intellisense. A VS Code setting for this extension could do something similar, at the 'user' or 'workspace' level.

So, on reconsideration, I'll add this to the feature-request backlog now.

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

No branches or pull requests

2 participants