Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Operator: Restriction level control should explain the meaning of selected value #13

Open
eparovyshnaya opened this issue Dec 8, 2022 · 0 comments
Open

Operator: Restriction level control should explain the meaning of selected value #13

eparovyshnaya opened this issue Dec 8, 2022 · 0 comments
Assignees
@eparovyshnaya
Milestone
2.3.3

Comments

@eparovyshnaya
Copy link

Restriction Level is a choise of {fatal, error, warning and info} and there are recommended processing for each level.

Despite it's finally up to development how to process each level, we should, nevertheless, explain the designed behaviour behind each of predefined levels.

Ported

from bugs.eclipse.org: 573729
Version: 1.1.0
from Eclipse Passage Issue 1001
@eparovyshnaya eparovyshnaya added this to the 2.3.3 milestone Dec 8, 2022
@eparovyshnaya eparovyshnaya self-assigned this Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eparovyshnaya eparovyshnaya

Labels
None yet
Projects
None yet
Milestone
2.3.3
Development

No branches or pull requests
1 participant
@eparovyshnaya