Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include top level type declarations in java-imports-scan-file #22

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

thejk
Copy link
Contributor

@thejk thejk commented Oct 8, 2021

Add new function java-imports-list-top-level and use it in java-imports-scan-file to add public top level types to list of classes to add to cache.

I find it useful when creating a new type or when opening a project for the first time to automatically get top level types added to the cache instead of having to import it at least once first.

Only works if java-imports-scan-file runs after type is declared in file so for new files it might be worth adding (java-imports-scan-file) to define-auto-insert for example.

No kotlin-mode support yet, haven't figured out a good way to do a "negative" match as "public" modifier is the default in kotlin. Also the primary constructor syntax is tricky to include and the regex is already rather horrible.

thejk added 2 commits November 6, 2022 19:02
In preparation for expanding the functionality, quite a bit of
setup needed but it seems to work.
Add new function java-imports-list-top-level and use it in
java-imports-scan-file to add public top level types to list
of classes to add to cache.

Useful when adding new types or working with a new project,
save having to specify the package on first import.
Only works if java-imports-scan-file runs after type is declared
in file so for new files it might be worth adding
(java-imports-scan-file) to define-auto-insert for example.

No kotlin-mode support yet, haven't figured out a good way
to do a "negative" match as "public" modifier is the default
in kotlin. Also the primary constructor syntax is tricky to include
and the regex is already rather horrible.
@thejk thejk force-pushed the include_toplevel_in_scan branch from b9a0105 to 7f9489f Compare November 6, 2022 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant