ddfreyne on main
Set up GitLab CI Merge branch 'gitlab-ci' into '… (compare)
ddfreyne on gitlab-ci
Set up GitLab CI wip (compare)
ddfreyne on debug-timeout
Debug why nanoc tests sometimes… (compare)
ddfreyne on default-listen-opts
ddfreyne on main
Use default Listen latency/wait… Merge pull request #1538 from n… (compare)
ddfreyne on default-listen-opts
Use default Listen latency/wait… (compare)
nanoc live
(the one that is provided by guard-nanoc) is a thin wrapper around both
what it the 'trick' in the blogging extension, why the question if items are frozen, and if, the data gets assigned to a variable just to return that
blk = -> { @items.select { |item| item[:kind] == 'article' } }
if @items.frozen?
@article_items ||= blk.call
else
blk.call
end
I can understsand that there might be some caching wanted, and that the result is returned if it exists
or does this something different?
but why the items.frozen question ? if this is not the case there is no caching, when is which branch relevant?
So, if you have one blog index page that depends on all individual articles, you could do e.g.
@items.find_all('/articles/*').each(&:path)
to force a dependency onto all those pages
A question to this ... what does it mean.. :-) , what does .each(&:path)
actually call on the item?
my ruby is not that strong, and from the doc I see there is a path property, but I am unsure how that relates, but I am very interested in understanding .
path
method on it
#path
makes Nanoc record a dependency onto the item that you called the #path
methd on)
piplelines
apropos check, I get 2 fails positives from the ilink checker, both to the same site , one time from the blog index and 1 time from an article linking to the same page, in both case the html is
<a href="/blog/2017/10/14/Using-SQLite3-in-your-C++-application.html">Using SQLite3 in your C++ application</a>
both links work... maybe the ++ in the URL?
wget https://a4z.gitlab.io/blog/2017/10/14/Using-SQLite3-in-your-C++-application.html
as being wrong,