2017-02-05 03:20:06 +00:00
|
|
|
// Copyright 2017 The Hugo Authors. All rights reserved.
|
|
|
|
//
|
|
|
|
// 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.
|
|
|
|
|
|
|
|
package commands
|
|
|
|
|
|
|
|
import (
|
Only re-render the view(s) you're working on
Hugo already, in its server mode, support partial rebuilds. To put it simply: If you change `about.md`, only that content page is read and processed, then Hugo does some processing (taxonomies etc.) and the full site is rendered.
This commit covers the rendering part: We now only re-render the pages you work on, i.e. the last n pages you watched in the browser (which obviously also includes the page in the example above).
To be more specific: When you are running the hugo server in watch (aka. livereload) mode, and change a template or a content file, then we do a partial re-rendering of the following:
* The current content page (if it is a content change)
* The home page
* Up to the last 10 pages you visited on the site.
This should in most cases be enough, but if you navigate to something completely different, you may see stale content. Doing an edit will then refresh that page.
Note that this feature is enabled by default. To turn it off, run `hugo server --disableFastRender`.
Fixes #3962
See #1643
2017-10-14 11:40:43 +00:00
|
|
|
"github.com/gohugoio/hugo/common/types"
|
2017-06-13 16:42:45 +00:00
|
|
|
"github.com/gohugoio/hugo/deps"
|
|
|
|
"github.com/gohugoio/hugo/helpers"
|
|
|
|
"github.com/gohugoio/hugo/hugofs"
|
2017-02-05 03:20:06 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
type commandeer struct {
|
|
|
|
*deps.DepsCfg
|
Only re-render the view(s) you're working on
Hugo already, in its server mode, support partial rebuilds. To put it simply: If you change `about.md`, only that content page is read and processed, then Hugo does some processing (taxonomies etc.) and the full site is rendered.
This commit covers the rendering part: We now only re-render the pages you work on, i.e. the last n pages you watched in the browser (which obviously also includes the page in the example above).
To be more specific: When you are running the hugo server in watch (aka. livereload) mode, and change a template or a content file, then we do a partial re-rendering of the following:
* The current content page (if it is a content change)
* The home page
* Up to the last 10 pages you visited on the site.
This should in most cases be enough, but if you navigate to something completely different, you may see stale content. Doing an edit will then refresh that page.
Note that this feature is enabled by default. To turn it off, run `hugo server --disableFastRender`.
Fixes #3962
See #1643
2017-10-14 11:40:43 +00:00
|
|
|
pathSpec *helpers.PathSpec
|
|
|
|
visitedURLs *types.EvictingStringQueue
|
|
|
|
configured bool
|
2017-02-05 03:20:06 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
func (c *commandeer) Set(key string, value interface{}) {
|
|
|
|
if c.configured {
|
|
|
|
panic("commandeer cannot be changed")
|
|
|
|
}
|
|
|
|
c.Cfg.Set(key, value)
|
|
|
|
}
|
|
|
|
|
|
|
|
// PathSpec lazily creates a new PathSpec, as all the paths must
|
|
|
|
// be configured before it is created.
|
|
|
|
func (c *commandeer) PathSpec() *helpers.PathSpec {
|
|
|
|
c.configured = true
|
|
|
|
return c.pathSpec
|
|
|
|
}
|
|
|
|
|
2017-03-25 18:48:28 +00:00
|
|
|
func (c *commandeer) initFs(fs *hugofs.Fs) error {
|
|
|
|
c.DepsCfg.Fs = fs
|
|
|
|
ps, err := helpers.NewPathSpec(fs, c.Cfg)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
c.pathSpec = ps
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2017-03-25 13:37:04 +00:00
|
|
|
func newCommandeer(cfg *deps.DepsCfg) (*commandeer, error) {
|
2017-03-25 18:48:28 +00:00
|
|
|
l := cfg.Language
|
|
|
|
if l == nil {
|
|
|
|
l = helpers.NewDefaultLanguage(cfg.Cfg)
|
|
|
|
}
|
|
|
|
ps, err := helpers.NewPathSpec(cfg.Fs, l)
|
2017-03-25 13:37:04 +00:00
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
Only re-render the view(s) you're working on
Hugo already, in its server mode, support partial rebuilds. To put it simply: If you change `about.md`, only that content page is read and processed, then Hugo does some processing (taxonomies etc.) and the full site is rendered.
This commit covers the rendering part: We now only re-render the pages you work on, i.e. the last n pages you watched in the browser (which obviously also includes the page in the example above).
To be more specific: When you are running the hugo server in watch (aka. livereload) mode, and change a template or a content file, then we do a partial re-rendering of the following:
* The current content page (if it is a content change)
* The home page
* Up to the last 10 pages you visited on the site.
This should in most cases be enough, but if you navigate to something completely different, you may see stale content. Doing an edit will then refresh that page.
Note that this feature is enabled by default. To turn it off, run `hugo server --disableFastRender`.
Fixes #3962
See #1643
2017-10-14 11:40:43 +00:00
|
|
|
|
|
|
|
return &commandeer{DepsCfg: cfg, pathSpec: ps, visitedURLs: types.NewEvictingStringQueue(10)}, nil
|
2017-02-05 03:20:06 +00:00
|
|
|
}
|