views: add action to delete repo

allow the user to delete a repo by selecting one and pressing the delete
button. Previous to deletion, show the user a confirmation page (a form)
with the details of the repo to delete

the confirmation form is constructed with the fields of Repoform.
RepoForm is also used in template used to create a repo. To make both
templates work with RepoForm, RepoForm's field 'create' has been renamed to
'submit'

ogcp.js: add a function to make that, when the user selects a
repository, the server in which it is contained is automatically
checked. We need it checked so that action_repo_delete can know the
server to which it has to send the delete request. Use data-server in
repos_details.html to make this work

Validate, in action_delete_repo, that user has only selected one repo to
delete. In order to do that, action_delete_repo view needs to be able to
get a list of all selected repos. This is only possible if <input>
elements that are associated with repos info contain a different name
attribute per repo. In this case, template repos.html has been modified
to use name={repo name}-{repo_id}.  After this, parse_elements() will
work and parse a set containing all selected repos.

modify html input associated to repos server in order to follow same
convention as in other templates. For example, images uses image-server;
scopes, scope-server.

1 files changed, 2 insertions, 1 deletions

diff --git a/ogcp/templates/actions/repos_details.html b/ogcp/templates/actions/repos_details.html
index 32b96bf..2768492 100644
--- a/ogcp/templates/actions/repos_details.html
+++ b/ogcp/templates/actions/repos_details.html
@@ -10,7 +10,8 @@
 <h1 class="m-5">{{_('Repo details')}}</h1>
 
 {{ wtf.quick_form(form,
+                  action=url_for('repo_add_post'),
                   method='post',
-                  button_map={'create': 'primary'},
+                  button_map={'submit': 'primary'},
                   extra_classes="mx-5") }}
 {% endblock %}