-
Notifications
You must be signed in to change notification settings - Fork 144
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
rough out plugin-standalone logic #10672 #10678
rough out plugin-standalone logic #10672 #10678
Conversation
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.
Great work on this. Nothing blocking a merge from my PoV. 👍
<meta name="description" content=""> | ||
<meta name="author" content=""> | ||
|
||
<link rel="shortcut icon" href="{% webpack_static 'favicons/favicon.ico' %}" type="image/x-icon" /> |
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.
A nice to have would be to use the icon listed in the Plugin row as the favicon. But this can be a followup. And also depends on whether we add font awesome here.
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'd caution against this for now. We'd need to remove support for using an .ico
file and instead just drop a plain <i>
tag in its place. Should be a good followup to allow users to upload a custom .ico defined in the Plugin db record.
@@ -33,13 +33,25 @@ def get(self, request, pluginid=None, slug=None): | |||
plugin = models.Plugin.objects.get(slug=slug) | |||
else: | |||
plugin = models.Plugin.objects.get(pk=pluginid) | |||
|
|||
if not request.user.has_perm("view_plugin", plugin): |
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.
In a follow-up, we might want to expose this as a config option as well. If my vue app desires to handle login itself, currently, this will redirect you to the arches auth page unnecessarily.
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.
Agreed 👍
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.
@chrabyrd my quick thoughts re: DRYing up the templates: I think that it makes sense to have a separate template for this and not try to inherit what is shared. I can imagine users wanting to customize this template specifically for standalone plugins (for example, changing favicons or themes) on an individual basis, which to me implies more drift in the shared parts of this and the base-manager.htm
template.
…nto 10672-cbyrd-vue-template-no-base-manager
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.
Great!
This reverts commit 038d7eb. Refs archesproject/arches#10678
Types of changes
Description of Change
This allows for plugins to be declared as "standalone", free from
knockout
and Arches chrome. Standalone plugins do not have their own js/template files and should instead be vue-onlySome things to consider:
config
field, shouldis_standalone
be its own column?base_base.htm
and updatingbase.htm
to inherit from it.ico
files<title>
could be updated to not have the application name, and instead just the plugin nameIssues Solved
#10672