[ 
https://issues.apache.org/jira/browse/AIRAVATA-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623956#comment-16623956
 ] 

ASF subversion and git services commented on AIRAVATA-2876:
-----------------------------------------------------------

Commit 1539cd49650f0f4863ae3db730bfd1c4e90b0f63 in airavata-django-portal's 
branch refs/heads/master from [~marcuschristie]
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=1539cd4 ]

AIRAVATA-2876 Navigate to route with save error


> Django: Application Editor (Module/Interface/Deployments)
> ---------------------------------------------------------
>
>                 Key: AIRAVATA-2876
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2876
>             Project: Airavata
>          Issue Type: Story
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> TODO
> * [x] Guard against unloading browser page when there are unsaved changes
> * [x] Only allow admins to edit applications and interfaces (need to guard 
> this on the backend as well)
> * [x] Use normal sharing rules to control who can edit a deployment
> * [ ] white background for application editor (custom background color based 
> on current route?)
> * [ ] enum selector component would be generally useful
> * [x] ordered list serializer field that orders output by a numeric field (on 
> read) and updates that numeric field (on write)
> * [x] CommandObjects editor and SetEnvPaths editor
> * [ ] transitions on input and output fields? (we now have synthetic keys for 
> them)
> * [ ] Do we really need the Vuex store? Maybe just have 
> ApplicationEditorContainer handle this logic in a simpler way
> * [x] load a list of all application modules instead of only "accessible" 
> modules
> * [x] fix setting id when saving module, interface, etc. 
> (registry-refactoring regression)
> * [x] delete application
> * [x] add sharing button to app deployment editor
> * [x] deployments aren't listed if there is no GroupResourceProfile for that 
> compute resource. Maybe only allow creating a deployment for compute 
> resources in GroupResourceProfiles? Or list deployments irrespective of 
> GroupResourceProfile?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to