SonarQube reports false unused imports in Vue3 Composition API

GueganVictor · July 14, 2021, 12:04pm

Hi,

I’ve recently created a new Vue 3 project and was playing around with the new script setup.
But SonarQube doesn’t seem to be able to match import in the script setup and its usage in the template.
In all my .vue using imports, SonarQube was giving false negative.

I’ve put a link below to the github repo to recreate the issue.

Scanner version : sonar-scanner-cli-4.6.2.2472-windows
Docker SonarQube version : 8.9.1.44547

Github repo : sonique

Thanks in advance for your time,

Victor GUEGAN

micDropper · September 15, 2021, 8:33pm

Yep, same issue for me. Also reports issues when importing *.vue components.

I believe SonarQube uses vue-eslint-parser to report these things according to this link:
https://jira.sonarsource.com/browse/MMF-1441

According to their release notes, vue-eslint-parser has implemented support for Vue’s new <script setup> syntax on July 1:

Sonar devs, please update this dependency to support Vue’s new SFC syntax. You can find the rfc for it here:

github.com

vuejs/rfcs/blob/master/active-rfcs/0040-script-setup.md

- Start Date: 2020-10-28
- Target Major Version: 3.x
- Reference Issues: https://github.com/vuejs/rfcs/pull/182
- Implementation PR: https://github.com/vuejs/vue-next/pull/2532

# Summary

Introduce a new script type in Single File Components: `<script setup>`, which exposes all its top level bindings to the template.

# Basic example

```html
<script setup>
  // imported components are also directly usable in template
  import Foo from './Foo.vue'
  import { ref } from 'vue'

  // write Composition API code just like in a normal setup()
  // but no need to manually return everything
  const count = ref(0)

This file has been truncated. show original

Yassin · October 8, 2021, 12:43pm

Hello Victor, hello Ethan,

Thank you for your messages, and welcome to SonarSource community.

We are indeed raising false-positives on the code snippet you provided, the reason being the version of the vue.js parser we use which doesn’t support this new syntax of Vue.js Single File Components.

I created a ticket to keep track of this issue and address it as soon as possible.

Regards,
Yassin

system · October 15, 2021, 12:44pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.