Some analyzers or transformers are misconfigured in .deepsource.toml. Please refer to the docs.
- ['github.com/kazimanzurrashid/aws-scheduler-go/graphql', 'github.com/kazimanzurrashid/aws-scheduler-go/collector', 'github.com/kazimanzurrashid/aws-scheduler-go/worker'] is not of type 'string' in meta for analyzer "go"
Avoid using wildcard imports JS-C1003
Anti-pattern
Minor
5 months ago
—
5 months old
Explicitly import the specific method needed
1import * as yup from 'yup'; 2import dayjs from 'dayjs';
3import debounce from 'lodash.debounce';
4import get from 'lodash.get';Explicitly import the specific method needed
1import * as yup from 'yup'; 2import get from 'lodash.get';
3import dayjs from 'dayjs';
4import DateFnsUtils from '@date-io/dayjs';
Description
Wildcard imports are easier to write, but make it harder to pick out the specific functions or objects from a dependency that are used in a file.
import * from 'module';
// there is no clear way to tell if
// `someFunction` has been imported
// from 'module'.
someFunction();
Therefore, it is recommended to explicit imports wherever possible.
NOTE: Some libraries do not expose themselves as ESModules. In cases like these, it is recommended to use a skipcq comment to suppress this issue.
Bad Practice
import * as axios from 'axios'
import * as Sentry from '@sentry/node'
try {
const result = await axios.get();
// ...
} catch (err) {
Sentry.captureException(err);
}
Recommended
import axios from 'axios'
// skipcq: JS-C1003 - sentry does not expose itself as an ES Module.
import * as Sentry from '@sentry/node'
try {
const result = await axios.get();
// ...
} catch (err) {
Sentry.captureException(err);
}