v1.14.2

ExplicitImports v1.14.2

Diff since v1.14.1

• Fix issue where explicitly imported macros aren't detected as imported. This may cause previously undetected stale explicit imports of macros to now be detected. (#159)
• Fix bug in kwarg default values, e.g. where f(; convert=convert) would not detect the usage of convert as external. (#148)
• Fix scoping issues in default values of positional arguments (#147), similar to above for kwargs
• Fix bug where if a field name in a struct was the same as the usage of a global in a constructor, that usage would be missed. (#146)
• Fix bug where names exported by Base and re-exported by other modules are incorrectly suggested to be explicitly imported from those other modules. (#145)

Merged pull requests:

• Filter out exported-from-Base names appropriately (#145) (@ericphanson)
• Handle field name shadowing issues (#111) (#146) (@ericphanson)
• Fix scoping issues with default values in function arguments (#147) (@ericphanson)
• Fix defaults for kwargs (#148) (@ericphanson)
• Add integration tests (#149) (@ericphanson)
• Install dependabot.yml (#150) (@giordano)
• Bump julia-actions/install-juliaup from 1 to 2 (#151) (@dependabot[bot])
• Bump actions/checkout from 4 to 6 (#152) (@dependabot[bot])
• Bump julia-actions/setup-julia from 1 to 2 (#153) (@dependabot[bot])
• Bump julia-actions/cache from 1 to 2 (#154) (@dependabot[bot])
• Bump codecov/codecov-action from 3 to 5 (#155) (@dependabot[bot])
• Add codecov configuration to exclude vendored code from coverage (#156) (@Copilot)
• add Ferrite integration tests (#157) (@ericphanson)
• Try fixing codecov (#158) (@ericphanson)
• [~breaking] Fix issue where explicitly imported macros aren't detected as imported (#159) (@ericphanson)
• Update version of Oceananigans for integration tests (#162) (@giordano)
• Bump project version from 1.14.1 to 1.14.2 for release (#163) (@ericphanson)

Closed issues:

• false positive in stale names with default value for function args (#62)
• Support earlier Julia versions (#65)
• unanalyzable not clearly defined (#79)
• submodules inside package extensions are not analyzable (#80)
• Exports from submodules that are using'd in parent module not required to be explicitly imported (#84)
• @argcheck false positive (#97)
• implicitly imported function with same name as kwarg not recognized (#98)
• imported name shadowed by field name (#111)
• Name shadowing of an import when assigning it to a function argument causes spurious unused import diagnostics (#120)
• print_explicit_imports suggests importing symbols from wrong module (#137)