Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Consider moving terminal ui to its own module

Open
  • Is something wrong?
#847 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
build-system, cli

Research direction

Begin by reviewing the core package's terminal UI code and the older flow components, then examine how the planned replacement of the core representation layer affects their placement. The work is done when terminal UI and those flow components live in a separate module and the Reactor dependency is no longer required by core.

Written by the indexing model from the issue text.

Description

area/components area/components-view

There's a lot of new code and while it's convenient to have it in a core package a new dependence to reactor is not optimal to have in a core itself. While we could try to make reactor optional it feels that separate module might be better. Not all want to use "UI" features.

At this point we also need to think older flow components as there is a plan to replace core representation layer in those to low level terminal ui components. This means those needs to live in a same module.

Dominant language
Java
Stars
826
Forks
404
Avg merge
6d 9h
Merged PRs (30d)
1

Getting set up

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 spring-projects/spring-shell

All issues in spring-projects/spring-shell

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.