VSCode extension and .zeplin/components.json not synced?

[fabiradi]

I'm starting to use the Zeplin extension for VSCode and was following the Getting started Guide. It is said that the extension will create (or ask to create) the config file. That never happened. All config seem to be "hidden" somewhere.

So, I manually created the config file zeplin/components.json using the CTRL+P command, added a styleguide and assigned components. Those information is not displayed in the extension panel. The components.json file does have actions included, i.e. "Add components", but it does not seem to be connected to the extension panel at all. So, the extension seems to be working somehow.

• What am I doing wrong?
• Where should I look next?

[fonurr]

Hello @fabiradi,

It is said that the extension will create (or ask to create) the config file. That never happened.

This was the case when the extension's sole purpose was to be used for Connected Components feature. Then, we updated the extension to have more features and removed that prompt because not all users use the Connected Components feature. We need to update the documentation though, thanks for the information. 👍

The components.json file does have actions included, i.e. "Add components", but it does not seem to be connected to the extension panel at all

That's because the extension panel is not related to Connected Components feature. It provides an easy access to Zeplin projects, styleguides, screens and components within VS Code. You have to add the projects or styleguides you use via the buttons on that panel. Connected Components configuration data may be integrated to extension panel in the future, but we haven't thought on that throughly yet.

For connected components feature, you can use ctrl/cmd + shift + P command and type "Zeplin" in the box to see which commands are available or use the buttons (CodeLens) on the config file that you mentioned.

[fabiradi]

Thanks for the quick response! It all makes sense. However, I think there is a lot of potential in using the sidebar in connection to the components.json file. I was at least expecting some kind of parsing of the file.

👍 The commands inside the file are very helpful, especially when adding component names.

What I would have liked to see:

• When a currently opened component (JSX) is configured to be connected to Zeplin, it could show just those information in the sidebar. They should be validated, if possible (zeplin names)

Thanks for the good work! I really like the connected components feature!