Skip to content

Conversation

AdamZalewski
Copy link
Contributor

@AdamZalewski AdamZalewski commented Feb 20, 2023

closes #120
closes #29

Tested - passes everything except ODBC on my side. Should fix the two issues referenced.

@AdamZalewski AdamZalewski requested a review from einarsi February 20, 2023 14:25
@einarsi einarsi changed the title feat: Error handle units and descriptions for empty tags fix: handle units and descriptions for empty tags Feb 24, 2023
units[tag] = unit
except:
if self.search(tag) == []: # check for nonexisting string
print("Tag not found: " + str(tag))
Copy link
Collaborator

Choose a reason for hiding this comment

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

We should really have used a logger, but since we haven't configured one I suggest to do:
warnings.warn(f"Tag not found: {tag}")
Same for get_description()

@einarsi
Copy link
Collaborator

einarsi commented Feb 24, 2023

What is this?
image

@asmfstatoil
Copy link
Collaborator

@mortendaehli Could you lift this issue on the priorities list?

@Asgmel03 Asgmel03 merged commit 5a7ccc2 into main Nov 18, 2024
16 checks passed
@Asgmel03 Asgmel03 deleted the get_units branch November 18, 2024 13: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.

Different behaviour get_descriptions and get_units when tag is not found Provide proper feedback to user when no data found for get_units() ++

4 participants