-
Notifications
You must be signed in to change notification settings - Fork 12
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
Issue #138 - Update GUI static file configuration parameters #178
Conversation
Hey @Futabay, thanks for throwing this up. It looks like there's some initial work that was done in line with this at https://github.com/NASA-AMMOS/AIT-GUI/blob/master/ait/gui/__init__.py#L282 I like the approach of keeping it internal to the Plugin better than globally. Perhaps the code in the plugin could be extended (if necessary for functionality) and documentation could be updated to reflect this config option in this PR? This is definitely something users will want to change so we want to make sure the options aren't hidden. This will also need updates pushed to Core config if there's still the "old" GUI config listed in there (note, I'm not sure there is, just a note for us to check that). |
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.
See prev comment for change ideas
Hi @MJJoyce, Thank you for the review. I will remove the line specifying |
Hey @Futabay, Thanks for throwing some changes. I apologize because I don't think I explained what I was getting at clearly in my previous post. Let me see if I can elaborate on what we want to see here vs what we have in We want all Plugin config to be passed via the "grouped plugin config" that users define in their server code. For the GUI we'd have something on the order of the following:
Extra plugin keys beyond the necessary name, inputs, and outputs are just passed along with the config to the Plugin during initialization and are accessible to the code. The
However, the current
It seems like the best approach is to default Thoughts? |
Hi @MJJoyce Is it a good idea to put this try/except clause inside of Lines 264 to 271 in 66dfe59
|
Changes look good @Futabay! What do you think about adding some logging into the try / except when we're updating the static file locations?
Would be nice to notify users if the path is set or if it's not. Regarding the other changes, seems reasonable to open a ticket to make that change as well. I'm not sure that there's anything relying on it existing outside of the plugin. We could review that on the other ticket though. |
ok! I will add the log, and create a separate ticket for the gui version log try/except clause |
ait/gui/__init__.py
Outdated
except: | ||
log.warn('[GUI Plugin Configuration] Unable to locate static file direcotry in config.yaml. '\ | ||
'The directory is set to {}'.format(HTMLRoot.User)) | ||
pass |
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.
Drop this pass
Changes look great! Thanks for the updates. There's an extra |
Hi @MJJoyce Sorry the pass was left in there. Change has been pushed. |
Awesome, thanks @Futabay! |
No description provided.