Add support for theme composition and inheritance
This commit adds support for theme composition and inheritance in Hugo.
With this, it helps thinking about a theme as a set of ordered components:
```toml
theme = ["my-shortcodes", "base-theme", "hyde"]
```
The theme definition example above in `config.toml` creates a theme with the 3 components with presedence from left to right.
So, Hugo will, for any given file, data entry etc., look first in the project, and then in `my-shortcode`, `base-theme` and lastly `hyde`.
Hugo uses two different algorithms to merge the filesystems, depending on the file type:
* For `i18n` and `data` files, Hugo merges deeply using the translation id and data key inside the files.
* For `static`, `layouts` (templates) and `archetypes` files, these are merged on file level. So the left-most file will be chosen.
The name used in the `theme` definition above must match a folder in `/your-site/themes`, e.g. `/your-site/themes/my-shortcodes`. There are plans to improve on this and get a URL scheme so this can be resolved automatically.
Also note that a component that is part of a theme can have its own configuration file, e.g. `config.toml`. There are currently some restrictions to what a theme component can configure:
* `params` (global and per language)
* `menu` (global and per language)
* `outputformats` and `mediatypes`
The same rules apply here: The left-most param/menu etc. with the same ID will win. There are some hidden and experimental namespace support in the above, which we will work to improve in the future, but theme authors are encouraged to create their own namespaces to avoid naming conflicts.
A final note: Themes/components can also have a `theme` definition in their `config.toml` and similar, which is the "inheritance" part of this commit's title. This is currently not supported by the Hugo theme site. We will have to wait for some "auto dependency" feature to be implemented for that to happen, but this can be a powerful feature if you want to create your own theme-variant based on others.
Fixes #4460
Fixes #4450
2018-03-01 09:01:25 -05:00
|
|
|
// Copyright 2018 The Hugo Authors. All rights reserved.
|
2016-08-07 16:01:55 -04:00
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
//
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
// limitations under the License.
|
|
|
|
|
Add support for theme composition and inheritance
This commit adds support for theme composition and inheritance in Hugo.
With this, it helps thinking about a theme as a set of ordered components:
```toml
theme = ["my-shortcodes", "base-theme", "hyde"]
```
The theme definition example above in `config.toml` creates a theme with the 3 components with presedence from left to right.
So, Hugo will, for any given file, data entry etc., look first in the project, and then in `my-shortcode`, `base-theme` and lastly `hyde`.
Hugo uses two different algorithms to merge the filesystems, depending on the file type:
* For `i18n` and `data` files, Hugo merges deeply using the translation id and data key inside the files.
* For `static`, `layouts` (templates) and `archetypes` files, these are merged on file level. So the left-most file will be chosen.
The name used in the `theme` definition above must match a folder in `/your-site/themes`, e.g. `/your-site/themes/my-shortcodes`. There are plans to improve on this and get a URL scheme so this can be resolved automatically.
Also note that a component that is part of a theme can have its own configuration file, e.g. `config.toml`. There are currently some restrictions to what a theme component can configure:
* `params` (global and per language)
* `menu` (global and per language)
* `outputformats` and `mediatypes`
The same rules apply here: The left-most param/menu etc. with the same ID will win. There are some hidden and experimental namespace support in the above, which we will work to improve in the future, but theme authors are encouraged to create their own namespaces to avoid naming conflicts.
A final note: Themes/components can also have a `theme` definition in their `config.toml` and similar, which is the "inheritance" part of this commit's title. This is currently not supported by the Hugo theme site. We will have to wait for some "auto dependency" feature to be implemented for that to happen, but this can be a powerful feature if you want to create your own theme-variant based on others.
Fixes #4460
Fixes #4450
2018-03-01 09:01:25 -05:00
|
|
|
package langs
|
2016-08-07 16:01:55 -04:00
|
|
|
|
|
|
|
import (
|
|
|
|
"sort"
|
|
|
|
"strings"
|
|
|
|
|
Add support for theme composition and inheritance
This commit adds support for theme composition and inheritance in Hugo.
With this, it helps thinking about a theme as a set of ordered components:
```toml
theme = ["my-shortcodes", "base-theme", "hyde"]
```
The theme definition example above in `config.toml` creates a theme with the 3 components with presedence from left to right.
So, Hugo will, for any given file, data entry etc., look first in the project, and then in `my-shortcode`, `base-theme` and lastly `hyde`.
Hugo uses two different algorithms to merge the filesystems, depending on the file type:
* For `i18n` and `data` files, Hugo merges deeply using the translation id and data key inside the files.
* For `static`, `layouts` (templates) and `archetypes` files, these are merged on file level. So the left-most file will be chosen.
The name used in the `theme` definition above must match a folder in `/your-site/themes`, e.g. `/your-site/themes/my-shortcodes`. There are plans to improve on this and get a URL scheme so this can be resolved automatically.
Also note that a component that is part of a theme can have its own configuration file, e.g. `config.toml`. There are currently some restrictions to what a theme component can configure:
* `params` (global and per language)
* `menu` (global and per language)
* `outputformats` and `mediatypes`
The same rules apply here: The left-most param/menu etc. with the same ID will win. There are some hidden and experimental namespace support in the above, which we will work to improve in the future, but theme authors are encouraged to create their own namespaces to avoid naming conflicts.
A final note: Themes/components can also have a `theme` definition in their `config.toml` and similar, which is the "inheritance" part of this commit's title. This is currently not supported by the Hugo theme site. We will have to wait for some "auto dependency" feature to be implemented for that to happen, but this can be a powerful feature if you want to create your own theme-variant based on others.
Fixes #4460
Fixes #4450
2018-03-01 09:01:25 -05:00
|
|
|
"github.com/gohugoio/hugo/common/maps"
|
2017-06-13 12:42:45 -04:00
|
|
|
"github.com/gohugoio/hugo/config"
|
2017-06-13 13:07:35 -04:00
|
|
|
"github.com/spf13/cast"
|
2016-08-07 16:01:55 -04:00
|
|
|
)
|
|
|
|
|
2016-10-24 07:45:30 -04:00
|
|
|
// These are the settings that should only be looked up in the global Viper
|
|
|
|
// config and not per language.
|
|
|
|
// This list may not be complete, but contains only settings that we know
|
|
|
|
// will be looked up in both.
|
|
|
|
// This isn't perfect, but it is ultimately the user who shoots him/herself in
|
|
|
|
// the foot.
|
|
|
|
// See the pathSpec.
|
|
|
|
var globalOnlySettings = map[string]bool{
|
|
|
|
strings.ToLower("defaultContentLanguageInSubdir"): true,
|
|
|
|
strings.ToLower("defaultContentLanguage"): true,
|
|
|
|
strings.ToLower("multilingual"): true,
|
2018-07-31 14:04:36 -04:00
|
|
|
strings.ToLower("assetDir"): true,
|
|
|
|
strings.ToLower("resourceDir"): true,
|
2016-10-24 07:45:30 -04:00
|
|
|
}
|
|
|
|
|
2017-08-02 08:25:05 -04:00
|
|
|
// Language manages specific-language configuration.
|
2016-08-07 16:01:55 -04:00
|
|
|
type Language struct {
|
2016-09-12 14:57:52 -04:00
|
|
|
Lang string
|
|
|
|
LanguageName string
|
|
|
|
Title string
|
|
|
|
Weight int
|
2017-02-04 22:20:06 -05:00
|
|
|
|
2018-03-21 12:21:46 -04:00
|
|
|
Disabled bool
|
|
|
|
|
|
|
|
// If set per language, this tells Hugo that all content files without any
|
|
|
|
// language indicator (e.g. my-page.en.md) is in this language.
|
|
|
|
// This is usually a path relative to the working dir, but it can be an
|
2018-07-07 05:40:47 -04:00
|
|
|
// absolute directory reference. It is what we get.
|
2018-03-21 12:21:46 -04:00
|
|
|
ContentDir string
|
|
|
|
|
2018-01-30 11:51:18 -05:00
|
|
|
Cfg config.Provider
|
|
|
|
|
|
|
|
// These are params declared in the [params] section of the language merged with the
|
|
|
|
// site's params, the most specific (language) wins on duplicate keys.
|
|
|
|
params map[string]interface{}
|
|
|
|
|
|
|
|
// These are config values, i.e. the settings declared outside of the [params] section of the language.
|
|
|
|
// This is the map Hugo looks in when looking for configuration values (baseURL etc.).
|
|
|
|
// Values in this map can also be fetched from the params map above.
|
|
|
|
settings map[string]interface{}
|
2016-08-07 16:01:55 -04:00
|
|
|
}
|
|
|
|
|
2016-08-08 07:55:18 -04:00
|
|
|
func (l *Language) String() string {
|
|
|
|
return l.Lang
|
|
|
|
}
|
|
|
|
|
2017-08-02 08:25:05 -04:00
|
|
|
// NewLanguage creates a new language.
|
2017-02-04 22:20:06 -05:00
|
|
|
func NewLanguage(lang string, cfg config.Provider) *Language {
|
2018-01-30 11:51:18 -05:00
|
|
|
// Note that language specific params will be overridden later.
|
|
|
|
// We should improve that, but we need to make a copy:
|
:sparkles: Implement Page bundling and image handling
This commit is not the smallest in Hugo's history.
Some hightlights include:
* Page bundles (for complete articles, keeping images and content together etc.).
* Bundled images can be processed in as many versions/sizes as you need with the three methods `Resize`, `Fill` and `Fit`.
* Processed images are cached inside `resources/_gen/images` (default) in your project.
* Symbolic links (both files and dirs) are now allowed anywhere inside /content
* A new table based build summary
* The "Total in nn ms" now reports the total including the handling of the files inside /static. So if it now reports more than you're used to, it is just **more real** and probably faster than before (see below).
A site building benchmark run compared to `v0.31.1` shows that this should be slightly faster and use less memory:
```bash
▶ ./benchSite.sh "TOML,num_langs=.*,num_root_sections=5,num_pages=(500|1000),tags_per_page=5,shortcodes,render"
benchmark old ns/op new ns/op delta
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 101785785 78067944 -23.30%
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 185481057 149159919 -19.58%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 103149918 85679409 -16.94%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 203515478 169208775 -16.86%
benchmark old allocs new allocs delta
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 532464 391539 -26.47%
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 1056549 772702 -26.87%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 555974 406630 -26.86%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 1086545 789922 -27.30%
benchmark old bytes new bytes delta
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 53243246 43598155 -18.12%
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 105811617 86087116 -18.64%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 54558852 44545097 -18.35%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 106903858 86978413 -18.64%
```
Fixes #3651
Closes #3158
Fixes #1014
Closes #2021
Fixes #1240
Updates #3757
2017-07-24 03:00:23 -04:00
|
|
|
params := make(map[string]interface{})
|
2018-01-30 11:51:18 -05:00
|
|
|
for k, v := range cfg.GetStringMap("params") {
|
|
|
|
params[k] = v
|
:sparkles: Implement Page bundling and image handling
This commit is not the smallest in Hugo's history.
Some hightlights include:
* Page bundles (for complete articles, keeping images and content together etc.).
* Bundled images can be processed in as many versions/sizes as you need with the three methods `Resize`, `Fill` and `Fit`.
* Processed images are cached inside `resources/_gen/images` (default) in your project.
* Symbolic links (both files and dirs) are now allowed anywhere inside /content
* A new table based build summary
* The "Total in nn ms" now reports the total including the handling of the files inside /static. So if it now reports more than you're used to, it is just **more real** and probably faster than before (see below).
A site building benchmark run compared to `v0.31.1` shows that this should be slightly faster and use less memory:
```bash
▶ ./benchSite.sh "TOML,num_langs=.*,num_root_sections=5,num_pages=(500|1000),tags_per_page=5,shortcodes,render"
benchmark old ns/op new ns/op delta
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 101785785 78067944 -23.30%
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 185481057 149159919 -19.58%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 103149918 85679409 -16.94%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 203515478 169208775 -16.86%
benchmark old allocs new allocs delta
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 532464 391539 -26.47%
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 1056549 772702 -26.87%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 555974 406630 -26.86%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 1086545 789922 -27.30%
benchmark old bytes new bytes delta
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 53243246 43598155 -18.12%
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 105811617 86087116 -18.64%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 54558852 44545097 -18.35%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 106903858 86978413 -18.64%
```
Fixes #3651
Closes #3158
Fixes #1014
Closes #2021
Fixes #1240
Updates #3757
2017-07-24 03:00:23 -04:00
|
|
|
}
|
Add support for theme composition and inheritance
This commit adds support for theme composition and inheritance in Hugo.
With this, it helps thinking about a theme as a set of ordered components:
```toml
theme = ["my-shortcodes", "base-theme", "hyde"]
```
The theme definition example above in `config.toml` creates a theme with the 3 components with presedence from left to right.
So, Hugo will, for any given file, data entry etc., look first in the project, and then in `my-shortcode`, `base-theme` and lastly `hyde`.
Hugo uses two different algorithms to merge the filesystems, depending on the file type:
* For `i18n` and `data` files, Hugo merges deeply using the translation id and data key inside the files.
* For `static`, `layouts` (templates) and `archetypes` files, these are merged on file level. So the left-most file will be chosen.
The name used in the `theme` definition above must match a folder in `/your-site/themes`, e.g. `/your-site/themes/my-shortcodes`. There are plans to improve on this and get a URL scheme so this can be resolved automatically.
Also note that a component that is part of a theme can have its own configuration file, e.g. `config.toml`. There are currently some restrictions to what a theme component can configure:
* `params` (global and per language)
* `menu` (global and per language)
* `outputformats` and `mediatypes`
The same rules apply here: The left-most param/menu etc. with the same ID will win. There are some hidden and experimental namespace support in the above, which we will work to improve in the future, but theme authors are encouraged to create their own namespaces to avoid naming conflicts.
A final note: Themes/components can also have a `theme` definition in their `config.toml` and similar, which is the "inheritance" part of this commit's title. This is currently not supported by the Hugo theme site. We will have to wait for some "auto dependency" feature to be implemented for that to happen, but this can be a powerful feature if you want to create your own theme-variant based on others.
Fixes #4460
Fixes #4450
2018-03-01 09:01:25 -05:00
|
|
|
maps.ToLower(params)
|
2018-03-21 12:21:46 -04:00
|
|
|
|
|
|
|
defaultContentDir := cfg.GetString("contentDir")
|
|
|
|
if defaultContentDir == "" {
|
|
|
|
panic("contentDir not set")
|
|
|
|
}
|
|
|
|
|
|
|
|
l := &Language{Lang: lang, ContentDir: defaultContentDir, Cfg: cfg, params: params, settings: make(map[string]interface{})}
|
:sparkles: Implement Page bundling and image handling
This commit is not the smallest in Hugo's history.
Some hightlights include:
* Page bundles (for complete articles, keeping images and content together etc.).
* Bundled images can be processed in as many versions/sizes as you need with the three methods `Resize`, `Fill` and `Fit`.
* Processed images are cached inside `resources/_gen/images` (default) in your project.
* Symbolic links (both files and dirs) are now allowed anywhere inside /content
* A new table based build summary
* The "Total in nn ms" now reports the total including the handling of the files inside /static. So if it now reports more than you're used to, it is just **more real** and probably faster than before (see below).
A site building benchmark run compared to `v0.31.1` shows that this should be slightly faster and use less memory:
```bash
▶ ./benchSite.sh "TOML,num_langs=.*,num_root_sections=5,num_pages=(500|1000),tags_per_page=5,shortcodes,render"
benchmark old ns/op new ns/op delta
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 101785785 78067944 -23.30%
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 185481057 149159919 -19.58%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 103149918 85679409 -16.94%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 203515478 169208775 -16.86%
benchmark old allocs new allocs delta
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 532464 391539 -26.47%
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 1056549 772702 -26.87%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 555974 406630 -26.86%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 1086545 789922 -27.30%
benchmark old bytes new bytes delta
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 53243246 43598155 -18.12%
BenchmarkSiteBuilding/TOML,num_langs=1,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 105811617 86087116 -18.64%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=500,tags_per_page=5,shortcodes,render-4 54558852 44545097 -18.35%
BenchmarkSiteBuilding/TOML,num_langs=3,num_root_sections=5,num_pages=1000,tags_per_page=5,shortcodes,render-4 106903858 86978413 -18.64%
```
Fixes #3651
Closes #3158
Fixes #1014
Closes #2021
Fixes #1240
Updates #3757
2017-07-24 03:00:23 -04:00
|
|
|
return l
|
2016-08-07 16:01:55 -04:00
|
|
|
}
|
|
|
|
|
2017-08-02 08:25:05 -04:00
|
|
|
// NewDefaultLanguage creates the default language for a config.Provider.
|
|
|
|
// If not otherwise specified the default is "en".
|
2017-02-04 22:20:06 -05:00
|
|
|
func NewDefaultLanguage(cfg config.Provider) *Language {
|
|
|
|
defaultLang := cfg.GetString("defaultContentLanguage")
|
2016-08-07 16:01:55 -04:00
|
|
|
|
|
|
|
if defaultLang == "" {
|
|
|
|
defaultLang = "en"
|
|
|
|
}
|
|
|
|
|
2017-02-04 22:20:06 -05:00
|
|
|
return NewLanguage(defaultLang, cfg)
|
2016-08-07 16:01:55 -04:00
|
|
|
}
|
|
|
|
|
2017-08-02 08:25:05 -04:00
|
|
|
// Languages is a sortable list of languages.
|
2016-08-07 16:01:55 -04:00
|
|
|
type Languages []*Language
|
|
|
|
|
2017-08-02 08:25:05 -04:00
|
|
|
// NewLanguages creates a sorted list of languages.
|
|
|
|
// NOTE: function is currently unused.
|
2016-08-07 16:01:55 -04:00
|
|
|
func NewLanguages(l ...*Language) Languages {
|
|
|
|
languages := make(Languages, len(l))
|
|
|
|
for i := 0; i < len(l); i++ {
|
|
|
|
languages[i] = l[i]
|
|
|
|
}
|
|
|
|
sort.Sort(languages)
|
|
|
|
return languages
|
|
|
|
}
|
|
|
|
|
|
|
|
func (l Languages) Len() int { return len(l) }
|
|
|
|
func (l Languages) Less(i, j int) bool { return l[i].Weight < l[j].Weight }
|
|
|
|
func (l Languages) Swap(i, j int) { l[i], l[j] = l[j], l[i] }
|
|
|
|
|
2017-08-02 08:25:05 -04:00
|
|
|
// Params retunrs language-specific params merged with the global params.
|
2016-08-07 16:01:55 -04:00
|
|
|
func (l *Language) Params() map[string]interface{} {
|
|
|
|
return l.params
|
|
|
|
}
|
|
|
|
|
2018-01-06 12:42:32 -05:00
|
|
|
// IsMultihost returns whether there are more than one language and at least one of
|
|
|
|
// the languages has baseURL specificed on the language level.
|
2017-11-02 03:25:20 -04:00
|
|
|
func (l Languages) IsMultihost() bool {
|
2018-01-06 12:42:32 -05:00
|
|
|
if len(l) <= 1 {
|
|
|
|
return false
|
|
|
|
}
|
|
|
|
|
2017-11-02 03:25:20 -04:00
|
|
|
for _, lang := range l {
|
|
|
|
if lang.GetLocal("baseURL") != nil {
|
|
|
|
return true
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return false
|
|
|
|
}
|
|
|
|
|
2018-01-30 11:51:18 -05:00
|
|
|
// SetParam sets a param with the given key and value.
|
2016-11-24 14:30:52 -05:00
|
|
|
// SetParam is case-insensitive.
|
2016-08-07 16:01:55 -04:00
|
|
|
func (l *Language) SetParam(k string, v interface{}) {
|
2016-10-24 07:45:30 -04:00
|
|
|
l.params[strings.ToLower(k)] = v
|
2016-08-07 16:01:55 -04:00
|
|
|
}
|
|
|
|
|
2016-11-21 16:59:33 -05:00
|
|
|
// GetBool returns the value associated with the key as a boolean.
|
|
|
|
func (l *Language) GetBool(key string) bool { return cast.ToBool(l.Get(key)) }
|
|
|
|
|
|
|
|
// GetString returns the value associated with the key as a string.
|
2016-08-07 16:01:55 -04:00
|
|
|
func (l *Language) GetString(key string) string { return cast.ToString(l.Get(key)) }
|
2016-08-12 04:12:01 -04:00
|
|
|
|
2016-11-21 16:59:33 -05:00
|
|
|
// GetInt returns the value associated with the key as an int.
|
|
|
|
func (l *Language) GetInt(key string) int { return cast.ToInt(l.Get(key)) }
|
|
|
|
|
|
|
|
// GetStringMap returns the value associated with the key as a map of interfaces.
|
|
|
|
func (l *Language) GetStringMap(key string) map[string]interface{} {
|
|
|
|
return cast.ToStringMap(l.Get(key))
|
2016-08-07 16:01:55 -04:00
|
|
|
}
|
|
|
|
|
2016-11-21 16:59:33 -05:00
|
|
|
// GetStringMapString returns the value associated with the key as a map of strings.
|
2016-08-07 16:01:55 -04:00
|
|
|
func (l *Language) GetStringMapString(key string) map[string]string {
|
|
|
|
return cast.ToStringMapString(l.Get(key))
|
|
|
|
}
|
|
|
|
|
2018-09-06 16:28:13 -04:00
|
|
|
// GetStringSlice returns the value associated with the key as a slice of strings.
|
2018-01-25 11:03:29 -05:00
|
|
|
func (l *Language) GetStringSlice(key string) []string {
|
|
|
|
return cast.ToStringSlice(l.Get(key))
|
|
|
|
}
|
|
|
|
|
2016-11-23 04:35:02 -05:00
|
|
|
// Get returns a value associated with the key relying on specified language.
|
2016-11-21 16:59:33 -05:00
|
|
|
// Get is case-insensitive for a key.
|
|
|
|
//
|
|
|
|
// Get returns an interface. For a specific value use one of the Get____ methods.
|
2016-08-07 16:01:55 -04:00
|
|
|
func (l *Language) Get(key string) interface{} {
|
2017-11-02 03:25:20 -04:00
|
|
|
local := l.GetLocal(key)
|
|
|
|
if local != nil {
|
|
|
|
return local
|
|
|
|
}
|
|
|
|
return l.Cfg.Get(key)
|
|
|
|
}
|
|
|
|
|
|
|
|
// GetLocal gets a configuration value set on language level. It will
|
|
|
|
// not fall back to any global value.
|
|
|
|
// It will return nil if a value with the given key cannot be found.
|
|
|
|
func (l *Language) GetLocal(key string) interface{} {
|
2016-08-07 16:01:55 -04:00
|
|
|
if l == nil {
|
|
|
|
panic("language not set")
|
|
|
|
}
|
|
|
|
key = strings.ToLower(key)
|
2016-10-24 07:45:30 -04:00
|
|
|
if !globalOnlySettings[key] {
|
2018-01-30 11:51:18 -05:00
|
|
|
if v, ok := l.settings[key]; ok {
|
2016-10-24 07:45:30 -04:00
|
|
|
return v
|
|
|
|
}
|
2016-08-07 16:01:55 -04:00
|
|
|
}
|
2017-11-02 03:25:20 -04:00
|
|
|
return nil
|
2017-02-04 22:20:06 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
// Set sets the value for the key in the language's params.
|
|
|
|
func (l *Language) Set(key string, value interface{}) {
|
|
|
|
if l == nil {
|
|
|
|
panic("language not set")
|
|
|
|
}
|
|
|
|
key = strings.ToLower(key)
|
2018-01-30 11:51:18 -05:00
|
|
|
l.settings[key] = value
|
2017-02-04 22:20:06 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
// IsSet checks whether the key is set in the language or the related config store.
|
|
|
|
func (l *Language) IsSet(key string) bool {
|
|
|
|
key = strings.ToLower(key)
|
|
|
|
|
|
|
|
key = strings.ToLower(key)
|
|
|
|
if !globalOnlySettings[key] {
|
2018-01-30 11:51:18 -05:00
|
|
|
if _, ok := l.settings[key]; ok {
|
2017-02-04 22:20:06 -05:00
|
|
|
return true
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return l.Cfg.IsSet(key)
|
|
|
|
|
2016-08-07 16:01:55 -04:00
|
|
|
}
|