-
Notifications
You must be signed in to change notification settings - Fork 24
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
Lumen Variations #49
Lumen Variations #49
Conversation
end = parser.parse(cells[idx + 1].string.split(" GMT")[0]) | ||
data["end"] = self.dt2ts(end) | ||
break | ||
if cells: |
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.
Can we invert this logic to reduce nesting?
if not cells:
continue
if cells[0].string == "Start" and cells[1].string == "End":
num_columns = 2
...
return [data] | ||
|
||
except Exception as exc: | ||
traceback.print_exc() |
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.
Should this be reverted? Or is it an intentional addition?
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.
Sorry, left over code. My bad
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.
LGTM
After looking at some email notifications I've spotted some varriations in the strings used to match data. There is also a possibility that a notification can have an empty table.
"scheduled maintenance #:"
can sometimes be used to identify the ID, and"This maintenance is scheduled"
can be used to find the status.Testing has been added to ensure these variations.