-
Notifications
You must be signed in to change notification settings - Fork 81
Larva Output Refactoring #8974
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.
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
Larva Output Refactoring #8974
Conversation
… LarvaMessages that can be used to return log messages in API calls that do not provide an output writer.
…which shouldn't be there anymore
@@ -52,6 +52,6 @@ public static LarvaLogLevel parse(String value, LarvaLogLevel defaultValue) { | |||
} | |||
|
|||
public boolean shouldLog(@Nullable LarvaLogLevel other) { | |||
return other == null || this.index <= other.index; | |||
return other == null || this.ordinal() <= other.ordinal(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👌
System.err.println("log.dir=" + System.getProperty("log.dir")); | ||
System.err.println("log.dir=" + AppConstants.getInstance().getProperty("log.dir")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is het handig deze twee de zelfde 'key' te geven?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, dat is wat debug-output die ik had toegevoegd omdat ik wou weten waarom iets mis ging. Was niet de bedoeling om dat te committen 🫣
|
Change Larva so it does not always need to have an outputstream available, but only when running scenarios (and core code only really depends on it for logs).
This is to enable Larva functionality to be called as library component, or from regular remote API calls.