Harmonize MigLayout specification composites

Open
#1,608 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
78/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
java
Domain
desktop

Research direction

Start by comparing CellSpecificationComposite.java and DimensionSpecificationComposite.java, focusing on their duplicated logging and string-handling behavior. Extract the common logging into an abstract base class, leaving each concrete composite to provide setString and getString; done means both implementations use the shared behavior without changing their functional results.

Written by the indexing model from the issue text.

Description

The CellSpecificationComposite and DimensionSpecificationComposite are functionally identical. We should extract the common logging into an abstract base class, then the actual implementations only need to implement a ´setString´ and ´getString´ method.

Dominant language
Java
Stars
97
Forks
34
Avg merge
1d 2h
Merged PRs (30d)
38

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 eclipse-windowbuilder/windowbuilder

All issues in eclipse-windowbuilder/windowbuilder

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.