ddfreyne on main
Enable binary compiled content … Merge branch 'enable-binary-com… (compare)
ddfreyne on enable-binary-compiled-content-cache
Enable binary compiled content … (compare)
ddfreyne on main
Use COW for binary compiled con… Merge branch 'binary-compiled-c… Make PostCompileItemRepView spe… (compare)
ddfreyne on enable-binary-compiled-content-cache
Merge branch 'binary-compiled-c… Enable binary compiled content … (compare)
ddfreyne on binary-compiled-content-cache-clonefile
Use COW for binary compiled con… (compare)
ddfreyne on main
Fix subtly broken PostCompileIt… (compare)
ddfreyne on binary-compiled-content-cache-clonefile
Use COW for binary compiled con… (compare)
ddfreyne on binary-compiled-content-cache-clonefile
Use COW for binary compiled con… (compare)
ddfreyne on main
Upgrade Rubocop (compare)
ddfreyne on enable-binary-compiled-content-cache
Enable binary compiled content … Use copy-on-write for binary co… (compare)
ddfreyne on main
Upgrade dependencies Use Bundler 2.x (compare)
ddfreyne on main
Upgrade nanoc, nanoc-live (compare)
ddfreyne on main
nanoc-live: Set version to 1.0.… nanoc-live: Add release notes f… Set version to 4.11.23 and 1 more (compare)
ddfreyne on 4.11.23
nanoc-live: Set version to 1.0.… nanoc-live: Add release notes f… Set version to 4.11.23 and 1 more (compare)
ddfreyne on nanoc-core-v4.11.23
nanoc-live: Set version to 1.0.… nanoc-live: Add release notes f… Set version to 4.11.23 and 1 more (compare)
ddfreyne on nanoc-cli-v4.11.23
nanoc-live: Set version to 1.0.… nanoc-live: Add release notes f… Set version to 4.11.23 and 1 more (compare)
ddfreyne on nanoc-live-v1.0.0b8
nanoc-live: Set version to 1.0.… nanoc-live: Add release notes f… Set version to 4.11.23 and 1 more (compare)
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,:read_snapshot
, with the two arguments being the rep and snapshot name, which then returns @item.compiled_content(rep: rep_name, snapshot: snapshot_name)