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

Add IntelliSense to Visual Studio for components #3454

Closed
dotnetnoobie opened this issue Jul 8, 2020 · 4 comments
Closed

Add IntelliSense to Visual Studio for components #3454

dotnetnoobie opened this issue Jul 8, 2020 · 4 comments
Assignees
Labels
closed:obsolete No longer valid community:request Issues specifically reported by a member of the community. feature A new feature

Comments

@dotnetnoobie
Copy link

dotnetnoobie commented Jul 8, 2020

What feature are you requesting?
Add IntelliSense to Visual Studio for components

What solution would be ideal for you?
IntelliSense for the standard FAST out of the box components and standard html element attributes & events
plus custom/third party components including custom attributes/properties & events

Also for child elements of components for example in fast-accordion element Visual Studio would know that it's child elements are fast-accordion-item and give a warning if a wrong component was used

Is there any additional context for your request?
Currently there is no IntelliSense in Visual Studio for even standard attributes on components like "class" etc.

@triage-new-issues triage-new-issues bot added the status:triage New Issue - needs triage label Jul 8, 2020
@nicholasrice nicholasrice added the improvement A non-feature-adding improvement label Jul 8, 2020
@triage-new-issues triage-new-issues bot removed the status:triage New Issue - needs triage label Jul 8, 2020
@EisenbergEffect EisenbergEffect added area:tools feature A new feature and removed improvement A non-feature-adding improvement labels Jul 20, 2020
@EisenbergEffect EisenbergEffect added the community:request Issues specifically reported by a member of the community. label Jul 24, 2020
@stale
Copy link

stale bot commented Dec 25, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the warning:stale No recent activity within a reasonable amount of time label Dec 25, 2020
@EisenbergEffect EisenbergEffect removed the warning:stale No recent activity within a reasonable amount of time label Mar 14, 2022
@EisenbergEffect
Copy link
Contributor

@williamw2 This is related to the custom element analyzer work. We should find out if VS Code understands the custom-elements.json file and if not, see how we can translate to enable this.

@ThorFjelldalen
Copy link

Is there any new status here? We have a design library written in FAST, but when importing it in other projects, VS Code has no knowledge of the web components in the library.

After browsing the Discord, I found some mentions of this, using Custom Elements Manifest. I tried using cem analyze --fast for generating a custom-elements.json, then referencing that file in the package.json of the library. I might have done something wrong, but I cannot get that to work. I cannot find any mentions of this in the official FAST docs either.

In the Discord, there were also someone with a working solution in SolidJS, but I'm not sure whether it would work in a project where the custom elements is inside a dependency. https://www.npmjs.com/package/custom-element-solidjs-integration

Anyone gotten intellisense to work for their design library written in FAST, in projects using that design library?

@janechu
Copy link
Collaborator

janechu commented May 28, 2024

Due to #6955 this would be more an issue for a library like https://github.com/microsoft/fluentui/tree/master/packages/web-components

@janechu janechu closed this as completed May 28, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in FAST Tools Roadmap May 28, 2024
@janechu janechu added the closed:obsolete No longer valid label May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed:obsolete No longer valid community:request Issues specifically reported by a member of the community. feature A new feature
Projects
None yet
Development

No branches or pull requests

6 participants