linter | Static Analysis Compiler Plugin for Scala | Code Analyzer library

I'm having an issue with the linting for my Vue SPA. I'm using the defineEmits function from the script setup syntactic sugar (https://v3.vuejs.org/api/sfc-script-setup.html). The errors just do not make any sense, does anyone know how to fix this (without disabling these rules for the affected files, because it happens to every usage of defineEmits). The weird thing is that the defineProps function works without errors, which follows the same syntax. Can anyone help me out here?

My linter complains about these errors:

I'm a bit confused about how to manage state withing a StatefulWidget. The following is a simplified example of a problem I am running into:

I have a StatefulWidget designed to display a list of things. It is constructed with a list that was retrieved from an API. The widget also allows the user to add new items to the list, hitting the API to do so. The API in turn returns the entire list after adding the item.

The challenge I'm running into is that the widget is constructed with an api.List object. Dart requires StatefulWdigets to be immutable (and therefore all of the fields final), and therefore the list cannot be replaced with a new list returned by the API when a user adds an item to it. That part makes sense to me: mutable state should live in the state object, not the widget. So that would suggest that the state object should keep track of the list. That leads to two different problems:

1. The state object is created in the createState method of the StatefulWidget. If we wanted to pass in the list to the constructor of the state object, the list would need to be stored as a final field on the StatefulWidget as well. Now both the widget and it's state object would have a reference to the list. As the user adds items to the list, and the state object replaces its list with the new copy returned from the API, the two would be out of sync.

2. Even if you did this, the linter will complain about including logic in the createState method: https://dart-lang.github.io/linter/lints/no_logic_in_create_state.html. It appears that they strongly suggest state objects should always have 0-argument constructors and you should never passing anything from the StatefulWidget to the State object. They suggest always accessing such data via the widget of the State object. But that leads you back to the problem of the StatefulWidget being immutable: you won't be able to replace the list if it is a final field on the StatefulWidget object.

Here, we avoid the linting issue of having logic in the createState method. But you cannot replace widget.list with newList since it is final.

I have an existing TypedDict containing multiple entries:

Firt of all, I am a total begginner in Rust, I started to use a code analyzer (Mega-Linter) and it made me realize how much I duplicated the same "use" statements in my submodules. Here what my source file tree looks like :

A static analysis tool I'm using prompts me that I need to std::forward the argument of the following function down the call chain:

I am currently setting up a boilerplate with React, Typescript, styled components, webpack etc. and I am getting an error when trying to run eslint:

Error: Must use import to load ES Module

Here is a more verbose version of the error:

I'm currently using isort --profile=black --line-length=79 as a linter in my project for python files.

This produces the Vertical Hanging Indent (mode 3 in isort's documentation kind of output:

A hook is checking, if there are impersonation information in storage persisted, when the page renders, and if so, sets those information in the global AppState context.

Up until today I haven't seen this dart code suggestions. I am happy to follow best practise, but to be honest, this makes no sense showing up in a stateful widget with no constructor. I thought it might be related to the @immutable annotation, but it doesn't seem to be and the dart documentation doesn't really help.

Dart Docs https://dart-lang.github.io/linter/lints/prefer_const_constructors.html

Code Suggestions in VSCode