Closed AmirMahdyJebreily closed 10 months ago
I’m glad to hear that the extension helped you!
As for identifying the configuration file in an existing project, I do think that it would be a good addition to automatically find the file. If you have another existing project, however, I believe that it should work if you simply right click on the file and click ‘Set as configuration file’.
For autocomplete not working in html files, I think this may be related to the previous issue, since intellisense does not show up until a configuration file is defined
I will close this issue once I make these changes (just so I don’t forget to do so).
Thanks for your feedback!
Thank you for your explanation!
Maybe the ability to automatically identify tailwind configuration files is a good idea!
Added in 1.1.8.7.
Hello my friend ! Thanks for this great repo. It helped our team to develop our Blazor Wasm application more quickly! I saw some bugs in this extension that you might want to solve! Unfortunately, I don't have a lot of time myself, but if I find time, I will definitely send a few big requests to your repository 😁
First of all, it cannot identify the configuration that was applied to the project before installing the extension! I had configured tailwindcss in a folder before my project folder, but after installing the extension, it forced me to put package.json between the project files!
Second, it didn't work in html documents, so I don't think it's related to the previous problem