`tapmoc.Severity` is not resolved when using FQDN
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 109
- Forks
- 6
- Avg merge
- 11m
- Merged PRs (30d)
- 3
Description
Description
This is because tapmoc (the package name) clashes with tapmoc (the autogenerated accessor)
Before:
After:
See https://youtrack.jetbrains.com/issue/KTIJ-26575/
See https://youtrack.jetbrains.com/issue/KTIJ-8463/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the FQDN reference to tapmoc.Severity and compare the reported behavior with KTIJ-26575 and KTIJ-8463. No source file or test is named in the issue; done means the package and autogenerated accessor no longer clash and tapmoc.Severity resolves correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100