Inconsistent imports

Open
#187 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
tooling

Research direction

Start by reproducing the generated Java compile error with the versions listed in the issue, then inspect the generator's import handling and configuration options. Done means generated assertions no longer produce conflicting imports and the choice between imports and fully qualified class names is configurable.

Written by the indexing model from the issue text.

Description

Problem:
I'm having classes generated with imports like:

import java.util.Objects;
import org.assertj.core.api.AbstractObjectAssert;
import org.assertj.core.internal.Iterables;
import org.assertj.core.util.Objects;

And this results in the compile error:

'java.util.Objects' is already defined in a single-type import

Solution:

I'd like to just use fully qualified class names instead of import statements.

I see https://github.com/assertj/assertj-assertions-generator/issues/97 requested using imports instead of fully qualified class names. Maybe both should be supported, but it should be configurable which one is being used.

Also it looks like this the use of fully qualified class names was already implemented for 2.2.1 with https://github.com/assertj/assertj-assertions-generator/commit/73d3c5e584e33b1509b058a2707c1ece00ee8bee?

Versions:
I'm using assertj-assertions-generator version 2.2.1, assertj-assertions-generator-maven-plugin version 2.2.0, and assertj-core version 3.21.0.

Dominant language
Java
Stars
72
Forks
47
PR merge metrics
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.