-
Notifications
You must be signed in to change notification settings - Fork 1
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
Extract XLSX logic + Add Data Dictionary + Add Artifacts #1263
base: main
Are you sure you want to change the base?
Conversation
35870e3
to
71f56c8
Compare
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.
I do think with formatted cells and rows, we're really talking about a Workbook
or Sheet
or Worksheet
here more so than a doc
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.
I know part of the idea is to abstract from that a bit, but I don't think we can quite escape it
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.
Maybe its a "formatted table"? "tabular report"? The crux of it seems to be these things that are undoubtedly worksheet tables, with some decoration/metadata that then a specific implementation gets to decide exactly how to dump it out
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.
I like tabular report. However, I do think you could pretty easily render this as HTML, so while it's currently just Excel workbooks, I think that might be overly specific.
Not to muddy the waters but have you looked at xlsxwriter? Seems to have a bit more support for formatting. Though it seems like you've managed to make things work pretty well with openpyxl |
ece315b
to
b859aca
Compare
b859aca
to
d41ce37
Compare
b217b1a
to
8edf256
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1263 +/- ##
==========================================
+ Coverage 69.67% 70.27% +0.59%
==========================================
Files 111 115 +4
Lines 5913 6142 +229
Branches 659 700 +41
==========================================
+ Hits 4120 4316 +196
- Misses 1661 1682 +21
- Partials 132 144 +12 ☔ View full report in Codecov by Sentry. |
f1e3a7a
to
b88fd84
Compare
8564331
to
2109c2c
Compare
@fvankrieken Yeah, I'd started with openpyxl because we were starting from an XSLX provided by OTI, whereas xlsxwriter can't do that. This is less of a consideration now that we're effectively generating everything, though I think it's nice to enable a template XLSX that could be used as a starter. On the flipside, openpyxl hasn't had a commit in nine years (maybe it didn't need any) however, it'd be pretty trivial at this point to switch over, as almost all the logic now lives in |
2109c2c
to
ac0fcc4
Compare
FYI, I'm going to do a real writeup on this tomorrow, and add docstrings to make this more readable. If you get there beforehand, the commits are quite atomic and could be easily read that way. Also, there are two tests that we'd expect to fail atm, since they rely on changes in the metadata repo here