Closed BijalBPatel closed 1 year ago
I'm confused about the "required" you seem to be reading this from the sheet itself? shouldn't we have this as a lookup in the default.py rather than counting on something that can be edited by a user?
Yeah in hindsight that's better. I didn't even think Abt users editing the documentation rows.
The benefit of pulling it from the sheet is that the rules and public documentation come from the same place (so they can't be mismatched).
It is more error prone this way tho and also it leads to the whole "you don't get validation if you import a sheet without header rows"
Probably better to just put it in defaults then.
Those are good points too… I like linking the documentation and defaults somehow…
Maybe the best would be to have all the header info ( default value , description, limits , type, example, etc) in defaults.py
Then generate the spreadsheet headers from that.
Then the wiki text from that as well.
It's technically possible just a lot of excel wrangling.
Ooh. Yeah that shouldn’t be too difficult I think… I can work on that.
On Sun, Mar 12, 2023 at 12:28 PM Bijal B. Patel @.***> wrote:
Maybe the best would be to have all the header info ( default value , description, limits , type) in defaults.py
Then generate the spreadsheet headers from that.
Then the wiki text from that as well.
It's technically possible just a lot of excel wrangling.
— Reply to this email directly, view it on GitHub https://github.com/NSLS-II-SST/rsoxs_scans/issues/24#issuecomment-1465241516, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI7VUOBHLIHH5LWYKEVV5SLW3YBSNANCNFSM6AAAAAAVWTE4J4 . You are receiving this because you commented.Message ID: @.***>