##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
vcs: Minimal change to expose the shadow repository...
vcs: Minimal change to expose the shadow repository Based on my original research, this was the "minimal" starting point. It shows that three concepts are needed for the "repo_name": * From the security standpoint we think of the shadow repository having the same ACL as the target repository of the pull request. This is because the pull request itself is considered to be a part of the target repository. Out of this thought, the variable "acl_repo_name" is used whenever we want to check permissions or when we need the database configuration of the repository. An alternative name would have been "db_repo_name", but the usage for ACL checking is the most important one. * From the web interaction perspective, we need the URL which was originally used to get to the repository. This is because based on this base URL commands can be identified. Especially for Git this is important, so that the commands are correctly recognized. Since the URL is in the focus, this is called "url_repo_name". * Finally we have to deal with the repository on the file system. This is what the VCS layer deal with normally, so this name is called "vcs_repo_name". The original repository interaction is a special case where all three names are the same. When interacting with a pull request, these three names are typically all different. This change is minimal in a sense that it just makes the interaction with a shadow repository barely work, without checking any special constraints yet. This was the starting point for further work on this topic.
lisaq - - Load All Authors

File last commit:

r822:133118c1 default
r887:175782be default
Show More
rhodecode-toast.html
30 lines | 1.3 KiB | text/html | HtmlLexer
/ rhodecode / public / js / src / components / rhodecode-toast / rhodecode-toast.html
History | Source | Raw |Copy content |Copy permalink
ergo
components: reorganize build pipeline to have nice separation of html/js/css
 r703 <link rel="import" href="../../../../../../bower_components/paper-button/paper-button.html">
ergo
polymer: simplify shared components
 r746 <link rel="import" href="../../../../../../bower_components/paper-toast/paper-toast.html">
ergo
components: reorganize build pipeline to have nice separation of html/js/css
 r703 <link rel="import" href="../rhodecode-unsafe-html/rhodecode-unsafe-html.html">
<dom-module id="rhodecode-toast">
<template>
ergo
notifications: make styling match the design
 r704 <style include="shared-styles"></style>
ergo
components: reorganize build pipeline to have nice separation of html/js/css
 r703 <link rel="stylesheet" href="rhodecode-toast.css">
ergo
notifications: clear out toasts after animation, remove ink animation from the button
 r778 <paper-toast id="p-toast"
duration="0"
horizontal-offset="100"
horizontal-align="auto"
vertical-align="top"
on-iron-overlay-closed="handleClosed"
always-on-top>
ergo
components: reorganize build pipeline to have nice separation of html/js/css
 r703 <div class="toast-message-holder">
<template is="dom-repeat" items="{{toasts}}">
ergo
toasts: refedined how notifications looks
 r747 <div class$="alert alert-{{item.level}}">
ergo
components: reorganize build pipeline to have nice separation of html/js/css
 r703 <rhodecode-unsafe-html text="{{item.message}}"></rhodecode-unsafe-html>
</div>
</template>
</div>
<div class="toast-close">
lisaq
notifications: move all notifications into polymer for consistency fix #4201
 r822 <button on-tap="dismissNotifications" class="btn btn-default">{{_gettext('Close')}}</button>
ergo
components: reorganize build pipeline to have nice separation of html/js/css
 r703 </div>
</paper-toast>
</template>
<script src="rhodecode-toast.js"></script>
</dom-module>