Open ljay79 opened 5 years ago
All valid stuff - too big to tackle in one issue though! :)
Ok if I close this now we have agreed standards? @ljay79
Pls keep open, as it also serves as a note for myself. Not everything of my above notes has been acomplished yet.
Entire code requires some review and enhancement of code documentation.
move all jira field functionalities (mapping, parsing, converting,..) into its own .gs file and maybe even into a nice class
refactor field parsing and mapping functionalities; review performance; redundant code; ... -- extended field data with flag indicating compatibility to update data back to Jira
rename functions and classes to be GAS private: trailing "_" underscore (https://developers.google.com/apps-script/guides/html/communication#private_functions)
create unified api response handler; error messages are handled everywhere almost the same way or different in each call - should be centralized and unified Sample:
to many individual single functions, most of them would make sense to combine into classes; more OO approach needed -- BTW: i started with transactional style too and then shifted over to OO style
change log level of (regular) JQL syntax errors; do show to user as error but do not log as error to StackDriver (flooding logs):