Use imports instead of fully qualified names

Open
#97 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
tooling

Research direction

Start by locating the generator entry point and the tests for generated XXXAssertions, then inspect how fully qualified type names are currently rendered. Done means generated assertions use imports where possible, retain a fully qualified name for package-name collisions, and have tests covering both cases.

Written by the indexing model from the issue text.

Description

I think it would be a nice addition if the generated XXXAssertions use imports for types. Of course if there are 2 types from different packages then one of them will have to have FQN

Dominant language
Java
Stars
72
Forks
47
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from assertj/assertj-generator

All issues in assertj/assertj-generator

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.