Sonarcloud: Unexpected unknown at-rule "#tailwind" - vue.js

Sonarcloud is reporting a bug in my Vue 3 application due to the Tailwind settings, however it is as in the documentation.
What is the best alternative in this case?

You can configure this rule in SonarCloud to ignore tailwind

You should configure the rules in sonarcloud.
The solution is on this page ->
https://himynameistim.com/blog/fixing-unexpected-unknown-at-rule-tailwind-in-sonar

Related

IntelliJ inspections not working after update to 2021.1

Suddenly the IntelliJ editor inspections have stopped working.
The syntax highlighting, the compiler errors and so on are not being shown.
The style highlighting works tough.
The inspections in the project navigation tree work and show compilation errors.
gradle build shows compilation errors too.
After updating to IntelliJ 2021.1, the Plugin for Swagger is not compatible anymore.
It seems to break the correct display of inspections.
Deinstalling the Plugin for Swagger helps. I was not able to find a better solution which allows me to keep using the Swagger Plugin.
GitHub issue reporting this problem: https://github.com/zalando/intellij-swagger/issues/325
Fun fact: this error popped out as I was trying to code a coding challenge for Zalando, the company which developed the Swagger Plugin :D.
Check idea.log (Help > Show Log in Explorer) for plugin exceptions and update / disable / reinstall the faulty plugin.
If by any chance, someone stumbles upon this answer and is developing with Ktor (with plugin), there's currently an issue that does the same thing as in asked question.
If your route method name and route path are the same - the IDE analyzer stops (issue link).
...
fun Route.redirect() { // <-- same word (redirect) = BAD
route("/redirect") { // <-- same word (redirect) = BAD
...
While the bug is being solved, you can just rename the route as a solution.

Directive AbstractStoreItemComponent in spartacus-storefront.d.ts has no selector, please add it

I am trying to integrate the new Spartacus UI in my Testing application (a classical mystore application built according to the recommendations bound to Spartacus).
Having built my "mystore" application, which I have tested, and works quite well based on electronic-store-spa... I have added the 7 tgz files in a row "lib" directory // to "mystore".
Then I have done my yarn add
yarn add ...
All seems to go well but it is getting worse when I do the Yarn start (last milestone of the checklist).
I get the following error :
"ERROR in Directive AbstractStoreItemComponent in /Users/muller/work/VariantKonfigurator/spartacus4VC/js-storefront/mystore/node_modules/#spartacus/storefront/spartacus-storefront.d.ts has no selector, please add it"
Looking in Spartacus-storefront.ts at the same level, I can see that there is a type: Directive
How can I overcome this error?
Thank you.

Using styleguidist in a react native application

I'm trying to use styleguidist in a react native application application;
I come across this link and implemented the exact same set up in my application:
https://github.com/styleguidist/react-styleguidist/tree/master/examples/react-native
After running npx styleguidist build, i got this output:
FAIL Failed to compile
build/bundle.f44bbfd4.js from UglifyJs
Unexpected token punc «:», expected punc «,» [build/bundle.f44bbfd4.js:372,1165]
Any ideas how to solve this ?
Thanks in advance.
Can you please provide more examples of what exact code changes you made and to what files? I had a similar issue and it turned out I was applying config changes to webpack.config.js that needed to go into the styleguide.config.js instead.

How to create an aurelia 1.0 app that can be deployed at any root location

I am trying to work out how to deploy an aurelia app, it runs in development with au run. but I need to deploy it into a path which is not the root of the web-site. ie at '/site' not '/'
when I deploy I get an exception from the router: ERROR [app-router] Error: Route not found: /site/
I think it may be that I need to specify a baseURL in one or more places?
but can't see how I can:
make it work in the development environment at /
make it work in the deployed environment at /[any-site-path]
avoid building in knowledge of '/[any-site-path]' to my development environment or bundles, as the path wont be known until someone comes to deploy the code?
i found this question but that seems to apply to an out of date version of the code.
I am using Aurelia 1.0 and building using the au-cli
Any pointers would be useful.
Looks like this is a bug that has been fixed in a more recent version.
I have just gone through and applied the latest versions of:
"aurelia-bootstrapper": "^1.0.0" -> "^2.1.1"
"aurelia-cli": "^0.24.0" -> "^0.26.1"
"aurelia-tools": "^0.2.2" -> "^1.0.0"
And i can now deploy my application to a site sub folder without specifying any url content in the code or html files!
So I can satisfy all 3 of the criteria in my question.
Note the aurelia-cli update (0.25.0) requires a change to the main.(ts/js) as mentioned in the release notes.

yii creating webapp error

Hi i am trying to create a yii application and i am got this issue tried google but not able to find the solution how can i resolve this,..?
This is my error:
Error: Unsupported VCS specified. Currently only git and hg supported.
And what actually this error is..?
yiic webapp d:\xampp\htdocs should work.
Notice the backslashes.
Or, perhaps better, since the app generator supports relative paths, navigate to d:\xampp and simply run yiic webapp htdocs.
That said: why are you using Yii 1 ?
It is really old, and does not receive any updates.
Yii 2 is so much better :)