re: request add css intellisense

[id-sakurata]

Add CSS Intellisense

• I'm the package's author and/or maintainer.
• I have have read the docs.
• I have tagged a release with a semver version number.
• My package repo has a description and a README describing what it's for and how to use it.
• My package doesn't add context menu entries. *
• My package doesn't add key bindings. **
• Any commands are available via the command palette.
• Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
• If my package is a syntax it doesn't also add a color scheme. ***
• If my package is a syntax it is named after the language it supports (without suffixes like "syntax" or "highlighting").
• I use .gitattributes to exclude files from the package: images, test files, sublime-project/workspace.

My package is CSS Intellisense

My package is similar to "IntelliSense for CSS class names in HTML" from vscode plugin. However it should still be added because it can make it easier to develop html without remembering the complete css class. you can use autocomplete from Css Intellisense.

[packagecontrol-bot]

Automated testing result: SUCCESS

Repo link: CSS Intellisense

Packages added:
  - CSS Intellisense

Processing package "CSS Intellisense"
  - All checks passed

[braver]

There are various important points in that checklist still open. Please ensure you covered all of that and then report back.

[braver]

I see you addressed most feedback from the previous PR. It's looking pretty good now, let's just see how it does out in the wild 😉

[id-sakurata]

I see you addressed most feedback from the previous PR. It's looking pretty good now, let's just see how it does out in the wild 😉

I really thank you for accepting my request. I can now recommend this plugin to my work friends 😆.

and now how do i update my plugin, i just found a problem when updating the settings, and now i have fixed the problem in the new update.

[braver]

how do i update my plugin

Any time you create a tag (with a higher version number), that will get pushed to users (typically when they start ST, or when they manually check for updates).