2017-06-02 10:43:44 +02:00
|
|
|
{{template "base/head" .}}
|
2023-02-01 23:56:10 +01:00
|
|
|
<div role="main" aria-label="{{.Title}}" class="page-content user settings organization">
|
2017-06-02 10:43:44 +02:00
|
|
|
{{template "user/settings/navbar" .}}
|
|
|
|
|
<div class="ui container">
|
|
|
|
|
{{template "base/alert" .}}
|
|
|
|
|
<h4 class="ui top attached header">
|
2022-06-27 22:58:46 +02:00
|
|
|
{{.locale.Tr "settings.orgs"}}
|
2017-06-02 10:43:44 +02:00
|
|
|
{{if .SignedUser.CanCreateOrganization}}
|
|
|
|
|
<div class="ui right">
|
2022-06-27 22:58:46 +02:00
|
|
|
<a class="ui primary tiny button" href="{{AppSubUrl}}/org/create">{{.locale.Tr "admin.orgs.new_orga"}}</a>
|
2017-06-02 10:43:44 +02:00
|
|
|
</div>
|
|
|
|
|
{{end}}
|
|
|
|
|
</h4>
|
|
|
|
|
<div class="ui attached segment orgs">
|
|
|
|
|
{{if .Orgs}}
|
|
|
|
|
<div class="ui middle aligned divided list">
|
|
|
|
|
{{range .Orgs}}
|
|
|
|
|
<div class="item">
|
|
|
|
|
<div class="right floated content">
|
2022-11-30 10:00:00 +01:00
|
|
|
<form>
|
2020-02-27 23:00:13 +01:00
|
|
|
{{$.CsrfTokenHtml}}
|
2022-11-30 10:00:00 +01:00
|
|
|
<button class="ui red button delete-button" data-modal-id="leave-organization"
|
|
|
|
|
data-url="{{.OrganisationLink}}/members/action/leave" data-datauid="{{$.SignedUser.ID}}"
|
|
|
|
|
data-name="{{$.SignedUser.DisplayName}}"
|
|
|
|
|
data-data-organization-name="{{.DisplayName}}">{{$.locale.Tr "org.members.leave"}}
|
|
|
|
|
</button>
|
2020-02-27 23:00:13 +01:00
|
|
|
</form>
|
2017-06-02 10:43:44 +02:00
|
|
|
</div>
|
Add context cache as a request level cache (#22294)
To avoid duplicated load of the same data in an HTTP request, we can set
a context cache to do that. i.e. Some pages may load a user from a
database with the same id in different areas on the same page. But the
code is hidden in two different deep logic. How should we share the
user? As a result of this PR, now if both entry functions accept
`context.Context` as the first parameter and we just need to refactor
`GetUserByID` to reuse the user from the context cache. Then it will not
be loaded twice on an HTTP request.
But of course, sometimes we would like to reload an object from the
database, that's why `RemoveContextData` is also exposed.
The core context cache is here. It defines a new context
```go
type cacheContext struct {
ctx context.Context
data map[any]map[any]any
lock sync.RWMutex
}
var cacheContextKey = struct{}{}
func WithCacheContext(ctx context.Context) context.Context {
return context.WithValue(ctx, cacheContextKey, &cacheContext{
ctx: ctx,
data: make(map[any]map[any]any),
})
}
```
Then you can use the below 4 methods to read/write/del the data within
the same context.
```go
func GetContextData(ctx context.Context, tp, key any) any
func SetContextData(ctx context.Context, tp, key, value any)
func RemoveContextData(ctx context.Context, tp, key any)
func GetWithContextCache[T any](ctx context.Context, cacheGroupKey string, cacheTargetID any, f func() (T, error)) (T, error)
```
Then let's take a look at how `system.GetString` implement it.
```go
func GetSetting(ctx context.Context, key string) (string, error) {
return cache.GetWithContextCache(ctx, contextCacheKey, key, func() (string, error) {
return cache.GetString(genSettingCacheKey(key), func() (string, error) {
res, err := GetSettingNoCache(ctx, key)
if err != nil {
return "", err
}
return res.SettingValue, nil
})
})
}
```
First, it will check if context data include the setting object with the
key. If not, it will query from the global cache which may be memory or
a Redis cache. If not, it will get the object from the database. In the
end, if the object gets from the global cache or database, it will be
set into the context cache.
An object stored in the context cache will only be destroyed after the
context disappeared.
2023-02-15 14:37:34 +01:00
|
|
|
{{avatar $.Context . 28 "mini"}}
|
2017-06-02 10:43:44 +02:00
|
|
|
<div class="content">
|
|
|
|
|
<a href="{{.HomeLink}}">{{.Name}}</a>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
{{end}}
|
|
|
|
|
</div>
|
2021-11-22 14:51:45 +01:00
|
|
|
{{template "base/paginate" .}}
|
2017-06-02 10:43:44 +02:00
|
|
|
{{else}}
|
2022-06-27 22:58:46 +02:00
|
|
|
{{.locale.Tr "settings.orgs_none"}}
|
2017-06-02 10:43:44 +02:00
|
|
|
{{end}}
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
2023-04-23 11:24:19 +02:00
|
|
|
<div class="ui gitea-confirm-modal delete modal" id="leave-organization">
|
|
|
|
|
<div class="header">
|
2022-11-30 10:00:00 +01:00
|
|
|
{{$.locale.Tr "org.members.leave"}}
|
|
|
|
|
</div>
|
|
|
|
|
<div class="content">
|
|
|
|
|
<p>{{$.locale.Tr "org.members.leave.detail" `<span class="dataOrganizationName"></span>` | Safe}}</p>
|
|
|
|
|
</div>
|
2023-04-23 11:24:19 +02:00
|
|
|
{{template "base/modal_actions_confirm" .}}
|
2022-11-30 10:00:00 +01:00
|
|
|
</div>
|
2017-06-02 10:43:44 +02:00
|
|
|
{{template "base/footer" .}}
|
