Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Allow `-clean` command line option with `-app` and `-resource` options

Offen
  • Stimmt etwas nicht?
#3,828 6 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Ruhig
Tech-Stack
java
Bereich
desktop

Rechercherichtung

Start by reading Phoebus's command-line handling for -clean, -app, and -resource, then trace how startup and requests are handled when Phoebus is already open. The issue does not name specific files or tests, so locate the relevant entry points and existing coverage first. Done means a clean launch opens the requested app or resource without restoring prior state, while an already-running instance ignores -clean and opens the request normally.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

We have a use case where we would want to launch a BOB screen in its own window from the terminal, e.g.

phoebus.sh -resource "file:/path/to/file/example.bob@target=window"

The only problem with this is that by default this will bring up the persisted Phoebus state, which might contain other open windows or screen editor tabs etc. At that point, the only way to ensure only the 'example.bob' screen appears is to make sure you close all the other windows/tabs before shutting phoebus down (not ideal!) or you first run with -clean:

phoebus.sh -clean
phoebus.sh -resource "file:/path/to/file/example.bob@target=window"

I feel like it would be much cleaner to be able to run something like:

phoebus.sh -clean -resource "file:/path/to/file/example.bob@target=window"

which is basically saying I want a clean start (no persisted state) and to open the following resource.

However the current design of Phoebus is such that -clean overrides any other option (e.g -resource xx, -app xx). Does anyone know the original reasoning behind this and whether we could change this behavior to something like that described above?

The desired behavior would be as such:

  • If Phoebus isn't open then clean (i.e. do not load previous state) and open the resource/app.
  • If Phoebus is already open, then the -clean is automatically ignored and the resource/app will just be opened as normal (and everything already open remains).

I am happy to put in a PR to make this change but wanted to get some feedback first to make sure I haven't missed anything about the behavior?

Vorherrschende Sprache
Java
Sterne
130
Forks
132
Ø Merge
2 T. 11 Std.
Gemergte PRs (30 T.)
19

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ControlSystemStudio/phoebus

Alle Issues in ControlSystemStudio/phoebus

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.