Skip to content

Releases: ericphanson/ExplicitImports.jl

v1.10.0

06 Oct 21:36
24b0de3
Compare
Choose a tag to compare

ExplicitImports v1.10.0

Diff since v1.9.0

Merged pull requests:

  • explicitly import parse (#78) (@palday)
  • Expand CLI functionality in main, make available on earlier Julia versions, and add .pre-commit-config.yaml (#86) (@abelsiqueira)
  • fix tests: allow DataAPI as source for groupby (#87) (@ericphanson)

Closed issues:

  • ExplicitImports has a colliding implicit import: parse (#77)
  • Include within precompile workload (#82)
  • Consider adding a pre-commit hook (#85)

v1.9.0

05 Jul 23:10
dc83d67
Compare
Choose a tag to compare

ExplicitImports v1.9.0

Diff since v1.8.0

Merged pull requests:

  • render markdown when printing, add @main entrypoint, add precompilation workload (#74) (@ericphanson)

v1.8.0

02 Jul 23:01
900a49f
Compare
Choose a tag to compare

ExplicitImports v1.8.0

Diff since v1.7.0

Merged pull requests:

  • use skip mechanism to skip imports/access of names from Compat that are owned by Base (#71) (@ericphanson)
  • support code-generated exports in staleness check (#72) (@ericphanson)

Closed issues:

  • Feature request: Reexport compatibility (#69)
  • Feature request: compatibility with Compat.jl (#70)

v1.7.0

02 Jul 20:47
44b9bee
Compare
Choose a tag to compare

ExplicitImports v1.7.0

Diff since v1.6.0

Merged pull requests:

v1.6.0

09 Jun 23:53
c45fa4a
Compare
Choose a tag to compare

ExplicitImports v1.6.0

Diff since v1.5.0

Merged pull requests:

  • WIP: add improper_explicit_imports that handles non-public and non-owner explicit imports, and add non-public results to improper_qualified_accesses (#28) (@ericphanson)
  • add check_all_explicit_imports_via_owners (#57) (@ericphanson)
  • improve coverage and deprecation warnings (#58) (@ericphanson)
  • add check_all_explicit_imports_are_public (#59) (@ericphanson)
  • add check all qualified accesses are public (#60) (@ericphanson)
  • By default, ignore "improper" imports/accesses from within the same package (#61) (@ericphanson)
  • document bug from #62 (#63) (@ericphanson)
  • add check_no_self_qualified_accesses (#64) (@ericphanson)

Closed issues:

  • Detect usage of non-public names? (#6)
  • Detect explicit imports from non-owning modules (#52)
  • Detect improper self-qualified names (#55)

v1.5.0

25 May 16:31
ba63bec
Compare
Choose a tag to compare

ExplicitImports v1.5.0

Diff since v1.4.5

Merged pull requests:

  • Provide functionality to detect "improper qualified access" (#50) (@ericphanson)

Closed issues:

  • Detect usage of names from Modules that don't own them (#48)

v1.4.5

25 May 16:23
ff24993
Compare
Choose a tag to compare

ExplicitImports v1.4.5

Diff since v1.4.4

Merged pull requests:

Closed issues:

  • modules exporting names which aren't theirs (#29)

v1.4.4

17 May 17:49
dbc3e05
Compare
Choose a tag to compare

ExplicitImports v1.4.4

Diff since v1.4.3

Merged pull requests:

v1.4.3

26 Apr 23:01
f166f50
Compare
Choose a tag to compare

ExplicitImports v1.4.3

Diff since v1.4.2

Merged pull requests:

v1.4.2

25 Apr 23:44
548a7d3
Compare
Choose a tag to compare

ExplicitImports v1.4.2

Diff since v1.4.1

  • improved parsing to squash several bugs causing false positives

Merged pull requests:

Closed issues:

  • types not correctly detected in function signature (#33)
  • False positive with type parameter that shadows name from imported package (#34)
  • False positive when unpacking loop variables (#35)
  • False positive with struct member name that shadows imported name (#36)