Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

selected-alternatives YAML List

See original GitHub issue

Description

When using the application.yaml, it would be nicer organizationally to support the quarkus.arc.selected-alternatives as a list. When adding many alternatives the line becomes very hard to read when common separated.

Current:

quarkus:
  arc:
    selected-alternatives: my.project.subproject.AlternativeA,my.project.subproject.AlternativeB,my.project.subproject.AlternativeC,my.project.subproject.AlternativeD

Proposed:

quarkus:
  arc:
    selected-alternatives: 
      - my.project.subproject1.AlternativeA
      - my.project.subproject1.AlternativeB
      - my.project.subproject1.AlternativeC
      - my.project.subproject1.AlternativeD

quarkus.arc.excluded-types is another good contender for this treatment.

Implementation ideas

No response

Issue Analytics

State:
Created 2 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

gsmetcommented, Feb 8, 2022

@mweber03 can you provide a small reproducer with instructions? That really helps us as it’s sometimes quite hard to reproduce the initial issue with partial information.

Thanks.

1reaction

mkoubacommented, Jan 31, 2022

@mweber03 @famod I’ve tried to use an application.yaml file as proposed in the description and it seems to work just fine.