2021-10-16 14:24:49 +00:00
|
|
|
// Copyright 2021 The Hugo Authors. All rights reserved.
|
Add Hugo Piper with SCSS support and much more
Before this commit, you would have to use page bundles to do image processing etc. in Hugo.
This commit adds
* A new `/assets` top-level project or theme dir (configurable via `assetDir`)
* A new template func, `resources.Get` which can be used to "get a resource" that can be further processed.
This means that you can now do this in your templates (or shortcodes):
```bash
{{ $sunset := (resources.Get "images/sunset.jpg").Fill "300x200" }}
```
This also adds a new `extended` build tag that enables powerful SCSS/SASS support with source maps. To compile this from source, you will also need a C compiler installed:
```
HUGO_BUILD_TAGS=extended mage install
```
Note that you can use output of the SCSS processing later in a non-SCSSS-enabled Hugo.
The `SCSS` processor is a _Resource transformation step_ and it can be chained with the many others in a pipeline:
```bash
{{ $css := resources.Get "styles.scss" | resources.ToCSS | resources.PostCSS | resources.Minify | resources.Fingerprint }}
<link rel="stylesheet" href="{{ $styles.RelPermalink }}" integrity="{{ $styles.Data.Digest }}" media="screen">
```
The transformation funcs above have aliases, so it can be shortened to:
```bash
{{ $css := resources.Get "styles.scss" | toCSS | postCSS | minify | fingerprint }}
<link rel="stylesheet" href="{{ $styles.RelPermalink }}" integrity="{{ $styles.Data.Digest }}" media="screen">
```
A quick tip would be to avoid the fingerprinting part, and possibly also the not-superfast `postCSS` when you're doing development, as it allows Hugo to be smarter about the rebuilding.
Documentation will follow, but have a look at the demo repo in https://github.com/bep/hugo-sass-test
New functions to create `Resource` objects:
* `resources.Get` (see above)
* `resources.FromString`: Create a Resource from a string.
New `Resource` transformation funcs:
* `resources.ToCSS`: Compile `SCSS` or `SASS` into `CSS`.
* `resources.PostCSS`: Process your CSS with PostCSS. Config file support (project or theme or passed as an option).
* `resources.Minify`: Currently supports `css`, `js`, `json`, `html`, `svg`, `xml`.
* `resources.Fingerprint`: Creates a fingerprinted version of the given Resource with Subresource Integrity..
* `resources.Concat`: Concatenates a list of Resource objects. Think of this as a poor man's bundler.
* `resources.ExecuteAsTemplate`: Parses and executes the given Resource and data context (e.g. .Site) as a Go template.
Fixes #4381
Fixes #4903
Fixes #4858
2018-02-20 09:02:14 +00: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.
|
|
|
|
|
2019-08-12 14:43:37 +00:00
|
|
|
package glob
|
Add Hugo Piper with SCSS support and much more
Before this commit, you would have to use page bundles to do image processing etc. in Hugo.
This commit adds
* A new `/assets` top-level project or theme dir (configurable via `assetDir`)
* A new template func, `resources.Get` which can be used to "get a resource" that can be further processed.
This means that you can now do this in your templates (or shortcodes):
```bash
{{ $sunset := (resources.Get "images/sunset.jpg").Fill "300x200" }}
```
This also adds a new `extended` build tag that enables powerful SCSS/SASS support with source maps. To compile this from source, you will also need a C compiler installed:
```
HUGO_BUILD_TAGS=extended mage install
```
Note that you can use output of the SCSS processing later in a non-SCSSS-enabled Hugo.
The `SCSS` processor is a _Resource transformation step_ and it can be chained with the many others in a pipeline:
```bash
{{ $css := resources.Get "styles.scss" | resources.ToCSS | resources.PostCSS | resources.Minify | resources.Fingerprint }}
<link rel="stylesheet" href="{{ $styles.RelPermalink }}" integrity="{{ $styles.Data.Digest }}" media="screen">
```
The transformation funcs above have aliases, so it can be shortened to:
```bash
{{ $css := resources.Get "styles.scss" | toCSS | postCSS | minify | fingerprint }}
<link rel="stylesheet" href="{{ $styles.RelPermalink }}" integrity="{{ $styles.Data.Digest }}" media="screen">
```
A quick tip would be to avoid the fingerprinting part, and possibly also the not-superfast `postCSS` when you're doing development, as it allows Hugo to be smarter about the rebuilding.
Documentation will follow, but have a look at the demo repo in https://github.com/bep/hugo-sass-test
New functions to create `Resource` objects:
* `resources.Get` (see above)
* `resources.FromString`: Create a Resource from a string.
New `Resource` transformation funcs:
* `resources.ToCSS`: Compile `SCSS` or `SASS` into `CSS`.
* `resources.PostCSS`: Process your CSS with PostCSS. Config file support (project or theme or passed as an option).
* `resources.Minify`: Currently supports `css`, `js`, `json`, `html`, `svg`, `xml`.
* `resources.Fingerprint`: Creates a fingerprinted version of the given Resource with Subresource Integrity..
* `resources.Concat`: Concatenates a list of Resource objects. Think of this as a poor man's bundler.
* `resources.ExecuteAsTemplate`: Parses and executes the given Resource and data context (e.g. .Site) as a Go template.
Fixes #4381
Fixes #4903
Fixes #4858
2018-02-20 09:02:14 +00:00
|
|
|
|
|
|
|
import (
|
2021-10-16 14:24:49 +00:00
|
|
|
"os"
|
2019-08-12 14:43:37 +00:00
|
|
|
"path"
|
|
|
|
"path/filepath"
|
2021-10-13 06:12:06 +00:00
|
|
|
"runtime"
|
2019-01-02 10:58:32 +00:00
|
|
|
"strings"
|
|
|
|
"sync"
|
Add Hugo Piper with SCSS support and much more
Before this commit, you would have to use page bundles to do image processing etc. in Hugo.
This commit adds
* A new `/assets` top-level project or theme dir (configurable via `assetDir`)
* A new template func, `resources.Get` which can be used to "get a resource" that can be further processed.
This means that you can now do this in your templates (or shortcodes):
```bash
{{ $sunset := (resources.Get "images/sunset.jpg").Fill "300x200" }}
```
This also adds a new `extended` build tag that enables powerful SCSS/SASS support with source maps. To compile this from source, you will also need a C compiler installed:
```
HUGO_BUILD_TAGS=extended mage install
```
Note that you can use output of the SCSS processing later in a non-SCSSS-enabled Hugo.
The `SCSS` processor is a _Resource transformation step_ and it can be chained with the many others in a pipeline:
```bash
{{ $css := resources.Get "styles.scss" | resources.ToCSS | resources.PostCSS | resources.Minify | resources.Fingerprint }}
<link rel="stylesheet" href="{{ $styles.RelPermalink }}" integrity="{{ $styles.Data.Digest }}" media="screen">
```
The transformation funcs above have aliases, so it can be shortened to:
```bash
{{ $css := resources.Get "styles.scss" | toCSS | postCSS | minify | fingerprint }}
<link rel="stylesheet" href="{{ $styles.RelPermalink }}" integrity="{{ $styles.Data.Digest }}" media="screen">
```
A quick tip would be to avoid the fingerprinting part, and possibly also the not-superfast `postCSS` when you're doing development, as it allows Hugo to be smarter about the rebuilding.
Documentation will follow, but have a look at the demo repo in https://github.com/bep/hugo-sass-test
New functions to create `Resource` objects:
* `resources.Get` (see above)
* `resources.FromString`: Create a Resource from a string.
New `Resource` transformation funcs:
* `resources.ToCSS`: Compile `SCSS` or `SASS` into `CSS`.
* `resources.PostCSS`: Process your CSS with PostCSS. Config file support (project or theme or passed as an option).
* `resources.Minify`: Currently supports `css`, `js`, `json`, `html`, `svg`, `xml`.
* `resources.Fingerprint`: Creates a fingerprinted version of the given Resource with Subresource Integrity..
* `resources.Concat`: Concatenates a list of Resource objects. Think of this as a poor man's bundler.
* `resources.ExecuteAsTemplate`: Parses and executes the given Resource and data context (e.g. .Site) as a Go template.
Fixes #4381
Fixes #4903
Fixes #4858
2018-02-20 09:02:14 +00:00
|
|
|
|
2019-01-02 10:58:32 +00:00
|
|
|
"github.com/gobwas/glob"
|
2019-08-12 14:43:37 +00:00
|
|
|
"github.com/gobwas/glob/syntax"
|
Add Hugo Piper with SCSS support and much more
Before this commit, you would have to use page bundles to do image processing etc. in Hugo.
This commit adds
* A new `/assets` top-level project or theme dir (configurable via `assetDir`)
* A new template func, `resources.Get` which can be used to "get a resource" that can be further processed.
This means that you can now do this in your templates (or shortcodes):
```bash
{{ $sunset := (resources.Get "images/sunset.jpg").Fill "300x200" }}
```
This also adds a new `extended` build tag that enables powerful SCSS/SASS support with source maps. To compile this from source, you will also need a C compiler installed:
```
HUGO_BUILD_TAGS=extended mage install
```
Note that you can use output of the SCSS processing later in a non-SCSSS-enabled Hugo.
The `SCSS` processor is a _Resource transformation step_ and it can be chained with the many others in a pipeline:
```bash
{{ $css := resources.Get "styles.scss" | resources.ToCSS | resources.PostCSS | resources.Minify | resources.Fingerprint }}
<link rel="stylesheet" href="{{ $styles.RelPermalink }}" integrity="{{ $styles.Data.Digest }}" media="screen">
```
The transformation funcs above have aliases, so it can be shortened to:
```bash
{{ $css := resources.Get "styles.scss" | toCSS | postCSS | minify | fingerprint }}
<link rel="stylesheet" href="{{ $styles.RelPermalink }}" integrity="{{ $styles.Data.Digest }}" media="screen">
```
A quick tip would be to avoid the fingerprinting part, and possibly also the not-superfast `postCSS` when you're doing development, as it allows Hugo to be smarter about the rebuilding.
Documentation will follow, but have a look at the demo repo in https://github.com/bep/hugo-sass-test
New functions to create `Resource` objects:
* `resources.Get` (see above)
* `resources.FromString`: Create a Resource from a string.
New `Resource` transformation funcs:
* `resources.ToCSS`: Compile `SCSS` or `SASS` into `CSS`.
* `resources.PostCSS`: Process your CSS with PostCSS. Config file support (project or theme or passed as an option).
* `resources.Minify`: Currently supports `css`, `js`, `json`, `html`, `svg`, `xml`.
* `resources.Fingerprint`: Creates a fingerprinted version of the given Resource with Subresource Integrity..
* `resources.Concat`: Concatenates a list of Resource objects. Think of this as a poor man's bundler.
* `resources.ExecuteAsTemplate`: Parses and executes the given Resource and data context (e.g. .Site) as a Go template.
Fixes #4381
Fixes #4903
Fixes #4858
2018-02-20 09:02:14 +00:00
|
|
|
)
|
|
|
|
|
2021-10-16 14:24:49 +00:00
|
|
|
const filepathSeparator = string(os.PathSeparator)
|
|
|
|
|
2021-10-13 06:12:06 +00:00
|
|
|
var (
|
|
|
|
isWindows = runtime.GOOS == "windows"
|
|
|
|
defaultGlobCache = &globCache{
|
2022-09-21 15:01:54 +00:00
|
|
|
isWindows: isWindows,
|
|
|
|
cache: make(map[string]globErr),
|
2021-10-13 06:12:06 +00:00
|
|
|
}
|
|
|
|
)
|
|
|
|
|
2020-10-05 18:01:52 +00:00
|
|
|
type globErr struct {
|
|
|
|
glob glob.Glob
|
|
|
|
err error
|
|
|
|
}
|
|
|
|
|
2021-10-13 06:12:06 +00:00
|
|
|
type globCache struct {
|
|
|
|
// Config
|
2022-09-21 15:01:54 +00:00
|
|
|
isWindows bool
|
2019-01-02 10:58:32 +00:00
|
|
|
|
2021-10-13 06:12:06 +00:00
|
|
|
// Cache
|
|
|
|
sync.RWMutex
|
|
|
|
cache map[string]globErr
|
2021-02-14 18:24:13 +00:00
|
|
|
}
|
|
|
|
|
2021-10-13 06:12:06 +00:00
|
|
|
func (gc *globCache) GetGlob(pattern string) (glob.Glob, error) {
|
2020-10-05 18:01:52 +00:00
|
|
|
var eg globErr
|
2019-01-02 10:58:32 +00:00
|
|
|
|
2021-10-13 06:12:06 +00:00
|
|
|
gc.RLock()
|
2020-10-05 18:01:52 +00:00
|
|
|
var found bool
|
2021-10-13 06:12:06 +00:00
|
|
|
eg, found = gc.cache[pattern]
|
|
|
|
gc.RUnlock()
|
2020-10-05 18:01:52 +00:00
|
|
|
if found {
|
|
|
|
return eg.glob, eg.err
|
2019-01-02 10:58:32 +00:00
|
|
|
}
|
|
|
|
|
2021-10-13 06:12:06 +00:00
|
|
|
var g glob.Glob
|
2020-10-05 18:01:52 +00:00
|
|
|
var err error
|
|
|
|
|
2021-10-13 06:12:06 +00:00
|
|
|
pattern = filepath.ToSlash(pattern)
|
2022-09-21 15:01:54 +00:00
|
|
|
g, err = glob.Compile(strings.ToLower(pattern), '/')
|
2021-10-13 06:12:06 +00:00
|
|
|
|
|
|
|
eg = globErr{
|
|
|
|
globDecorator{
|
2022-09-21 15:01:54 +00:00
|
|
|
g: g,
|
all: Rework page store, add a dynacache, improve partial rebuilds, and some general spring cleaning
There are some breaking changes in this commit, see #11455.
Closes #11455
Closes #11549
This fixes a set of bugs (see issue list) and it is also paying some technical debt accumulated over the years. We now build with Staticcheck enabled in the CI build.
The performance should be about the same as before for regular sized Hugo sites, but it should perform and scale much better to larger data sets, as objects that uses lots of memory (e.g. rendered Markdown, big JSON files read into maps with transform.Unmarshal etc.) will now get automatically garbage collected if needed. Performance on partial rebuilds when running the server in fast render mode should be the same, but the change detection should be much more accurate.
A list of the notable new features:
* A new dependency tracker that covers (almost) all of Hugo's API and is used to do fine grained partial rebuilds when running the server.
* A new and simpler tree document store which allows fast lookups and prefix-walking in all dimensions (e.g. language) concurrently.
* You can now configure an upper memory limit allowing for much larger data sets and/or running on lower specced PCs.
We have lifted the "no resources in sub folders" restriction for branch bundles (e.g. sections).
Memory Limit
* Hugos will, by default, set aside a quarter of the total system memory, but you can set this via the OS environment variable HUGO_MEMORYLIMIT (in gigabytes). This is backed by a partitioned LRU cache used throughout Hugo. A cache that gets dynamically resized in low memory situations, allowing Go's Garbage Collector to free the memory.
New Dependency Tracker: Hugo has had a rule based coarse grained approach to server rebuilds that has worked mostly pretty well, but there have been some surprises (e.g. stale content). This is now revamped with a new dependency tracker that can quickly calculate the delta given a changed resource (e.g. a content file, template, JS file etc.). This handles transitive relations, e.g. $page -> js.Build -> JS import, or $page1.Content -> render hook -> site.GetPage -> $page2.Title, or $page1.Content -> shortcode -> partial -> site.RegularPages -> $page2.Content -> shortcode ..., and should also handle changes to aggregated values (e.g. site.Lastmod) effectively.
This covers all of Hugo's API with 2 known exceptions (a list that may not be fully exhaustive):
Changes to files loaded with template func os.ReadFile may not be handled correctly. We recommend loading resources with resources.Get
Changes to Hugo objects (e.g. Page) passed in the template context to lang.Translate may not be detected correctly. We recommend having simple i18n templates without too much data context passed in other than simple types such as strings and numbers.
Note that the cachebuster configuration (when A changes then rebuild B) works well with the above, but we recommend that you revise that configuration, as it in most situations should not be needed. One example where it is still needed is with TailwindCSS and using changes to hugo_stats.json to trigger new CSS rebuilds.
Document Store: Previously, a little simplified, we split the document store (where we store pages and resources) in a tree per language. This worked pretty well, but the structure made some operations harder than they needed to be. We have now restructured it into one Radix tree for all languages. Internally the language is considered to be a dimension of that tree, and the tree can be viewed in all dimensions concurrently. This makes some operations re. language simpler (e.g. finding translations is just a slice range), but the idea is that it should also be relatively inexpensive to add more dimensions if needed (e.g. role).
Fixes #10169
Fixes #10364
Fixes #10482
Fixes #10630
Fixes #10656
Fixes #10694
Fixes #10918
Fixes #11262
Fixes #11439
Fixes #11453
Fixes #11457
Fixes #11466
Fixes #11540
Fixes #11551
Fixes #11556
Fixes #11654
Fixes #11661
Fixes #11663
Fixes #11664
Fixes #11669
Fixes #11671
Fixes #11807
Fixes #11808
Fixes #11809
Fixes #11815
Fixes #11840
Fixes #11853
Fixes #11860
Fixes #11883
Fixes #11904
Fixes #7388
Fixes #7425
Fixes #7436
Fixes #7544
Fixes #7882
Fixes #7960
Fixes #8255
Fixes #8307
Fixes #8863
Fixes #8927
Fixes #9192
Fixes #9324
2023-12-24 18:11:05 +00:00
|
|
|
isWindows: gc.isWindows,
|
|
|
|
},
|
2021-10-13 06:12:06 +00:00
|
|
|
err,
|
|
|
|
}
|
|
|
|
|
|
|
|
gc.Lock()
|
|
|
|
gc.cache[pattern] = eg
|
|
|
|
gc.Unlock()
|
2020-10-05 18:01:52 +00:00
|
|
|
|
|
|
|
return eg.glob, eg.err
|
Add Hugo Piper with SCSS support and much more
Before this commit, you would have to use page bundles to do image processing etc. in Hugo.
This commit adds
* A new `/assets` top-level project or theme dir (configurable via `assetDir`)
* A new template func, `resources.Get` which can be used to "get a resource" that can be further processed.
This means that you can now do this in your templates (or shortcodes):
```bash
{{ $sunset := (resources.Get "images/sunset.jpg").Fill "300x200" }}
```
This also adds a new `extended` build tag that enables powerful SCSS/SASS support with source maps. To compile this from source, you will also need a C compiler installed:
```
HUGO_BUILD_TAGS=extended mage install
```
Note that you can use output of the SCSS processing later in a non-SCSSS-enabled Hugo.
The `SCSS` processor is a _Resource transformation step_ and it can be chained with the many others in a pipeline:
```bash
{{ $css := resources.Get "styles.scss" | resources.ToCSS | resources.PostCSS | resources.Minify | resources.Fingerprint }}
<link rel="stylesheet" href="{{ $styles.RelPermalink }}" integrity="{{ $styles.Data.Digest }}" media="screen">
```
The transformation funcs above have aliases, so it can be shortened to:
```bash
{{ $css := resources.Get "styles.scss" | toCSS | postCSS | minify | fingerprint }}
<link rel="stylesheet" href="{{ $styles.RelPermalink }}" integrity="{{ $styles.Data.Digest }}" media="screen">
```
A quick tip would be to avoid the fingerprinting part, and possibly also the not-superfast `postCSS` when you're doing development, as it allows Hugo to be smarter about the rebuilding.
Documentation will follow, but have a look at the demo repo in https://github.com/bep/hugo-sass-test
New functions to create `Resource` objects:
* `resources.Get` (see above)
* `resources.FromString`: Create a Resource from a string.
New `Resource` transformation funcs:
* `resources.ToCSS`: Compile `SCSS` or `SASS` into `CSS`.
* `resources.PostCSS`: Process your CSS with PostCSS. Config file support (project or theme or passed as an option).
* `resources.Minify`: Currently supports `css`, `js`, `json`, `html`, `svg`, `xml`.
* `resources.Fingerprint`: Creates a fingerprinted version of the given Resource with Subresource Integrity..
* `resources.Concat`: Concatenates a list of Resource objects. Think of this as a poor man's bundler.
* `resources.ExecuteAsTemplate`: Parses and executes the given Resource and data context (e.g. .Site) as a Go template.
Fixes #4381
Fixes #4903
Fixes #4858
2018-02-20 09:02:14 +00:00
|
|
|
}
|
2019-08-12 14:43:37 +00:00
|
|
|
|
2023-05-21 12:25:16 +00:00
|
|
|
// Or creates a new Glob from the given globs.
|
|
|
|
func Or(globs ...glob.Glob) glob.Glob {
|
|
|
|
return globSlice{globs: globs}
|
|
|
|
}
|
|
|
|
|
|
|
|
// MatchesFunc is a convenience type to create a glob.Glob from a function.
|
|
|
|
type MatchesFunc func(s string) bool
|
|
|
|
|
|
|
|
func (m MatchesFunc) Match(s string) bool {
|
|
|
|
return m(s)
|
|
|
|
}
|
|
|
|
|
|
|
|
type globSlice struct {
|
|
|
|
globs []glob.Glob
|
|
|
|
}
|
|
|
|
|
|
|
|
func (g globSlice) Match(s string) bool {
|
|
|
|
for _, g := range g.globs {
|
|
|
|
if g.Match(s) {
|
|
|
|
return true
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return false
|
|
|
|
}
|
|
|
|
|
2021-10-13 06:12:06 +00:00
|
|
|
type globDecorator struct {
|
|
|
|
// On Windows we may get filenames with Windows slashes to match,
|
2023-02-18 20:47:35 +00:00
|
|
|
// which we need to normalize.
|
2021-10-13 06:12:06 +00:00
|
|
|
isWindows bool
|
|
|
|
|
|
|
|
g glob.Glob
|
|
|
|
}
|
|
|
|
|
|
|
|
func (g globDecorator) Match(s string) bool {
|
|
|
|
if g.isWindows {
|
|
|
|
s = filepath.ToSlash(s)
|
|
|
|
}
|
2022-09-23 11:54:09 +00:00
|
|
|
s = strings.ToLower(s)
|
2021-10-13 06:12:06 +00:00
|
|
|
return g.g.Match(s)
|
|
|
|
}
|
|
|
|
|
|
|
|
func GetGlob(pattern string) (glob.Glob, error) {
|
|
|
|
return defaultGlobCache.GetGlob(pattern)
|
|
|
|
}
|
|
|
|
|
2019-08-12 14:43:37 +00:00
|
|
|
func NormalizePath(p string) string {
|
2022-09-23 11:54:09 +00:00
|
|
|
return strings.ToLower(NormalizePathNoLower(p))
|
2019-08-12 14:43:37 +00:00
|
|
|
}
|
|
|
|
|
2022-09-23 11:54:09 +00:00
|
|
|
func NormalizePathNoLower(p string) string {
|
2022-09-21 15:01:54 +00:00
|
|
|
return strings.Trim(path.Clean(filepath.ToSlash(p)), "/.")
|
|
|
|
}
|
|
|
|
|
2019-08-12 14:43:37 +00:00
|
|
|
// ResolveRootDir takes a normalized path on the form "assets/**.json" and
|
|
|
|
// determines any root dir, i.e. any start path without any wildcards.
|
|
|
|
func ResolveRootDir(p string) string {
|
|
|
|
parts := strings.Split(path.Dir(p), "/")
|
|
|
|
var roots []string
|
|
|
|
for _, part := range parts {
|
2019-08-13 10:35:04 +00:00
|
|
|
if HasGlobChar(part) {
|
2019-08-12 14:43:37 +00:00
|
|
|
break
|
|
|
|
}
|
|
|
|
roots = append(roots, part)
|
|
|
|
}
|
|
|
|
|
|
|
|
if len(roots) == 0 {
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
return strings.Join(roots, "/")
|
|
|
|
}
|
2019-08-13 10:35:04 +00:00
|
|
|
|
|
|
|
// FilterGlobParts removes any string with glob wildcard.
|
|
|
|
func FilterGlobParts(a []string) []string {
|
|
|
|
b := a[:0]
|
|
|
|
for _, x := range a {
|
|
|
|
if !HasGlobChar(x) {
|
|
|
|
b = append(b, x)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return b
|
|
|
|
}
|
|
|
|
|
|
|
|
// HasGlobChar returns whether s contains any glob wildcards.
|
|
|
|
func HasGlobChar(s string) bool {
|
|
|
|
for i := 0; i < len(s); i++ {
|
|
|
|
if syntax.Special(s[i]) {
|
|
|
|
return true
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return false
|
|
|
|
}
|