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.

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

fix: Fix duplication of logging messages #59

Merged
merged 5 commits into from
Feb 29, 2024
Merged

fix: Fix duplication of logging messages #59

merged 5 commits into from
Feb 29, 2024

Conversation

ewuerger
Copy link
Member

@ewuerger ewuerger commented Feb 27, 2024

Closes #17. Wouldn't go as far as #30 describes for now.

The commits will be squashed.

@ewuerger ewuerger self-assigned this Feb 27, 2024
@ewuerger ewuerger force-pushed the fix-logging branch 2 times, most recently from ff4d3e3 to ce32fad Compare February 27, 2024 15:07
Copy link
Collaborator

@micha91 micha91 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In addition to the requested changes, I would also propose to move the error messages to constants. This would really help us, when we one day want to produce the error/warning report

capella2polarion/converters/element_converter.py Outdated Show resolved Hide resolved
capella2polarion/converters/element_converter.py Outdated Show resolved Hide resolved
Copy link
Collaborator

@micha91 micha91 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM except for the log message itself

capella2polarion/converters/element_converter.py Outdated Show resolved Hide resolved
@ewuerger ewuerger merged commit 9b6909c into main Feb 29, 2024
0 of 5 checks passed
@ewuerger ewuerger deleted the fix-logging branch February 29, 2024 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Separate log messages by using the right types
2 participants