ddfreyne changed the topic of #nanoc to: 3.8.0 (May 4th) - 4.0.0rc2 (July 11th) | web http://nanoc.ws/ | repo http://bit.ly/XE6e3G | issues http://bit.ly/VfXaSV | forum http://ho.io/n-discuss | irclog http://irclog.whitequark.org/nanoc
kAworu has quit [Remote host closed the connection]
kAworu has joined #nanoc
<guardian> o/
<ddfreyne> VitamineD: There are no reps at preprocessing time
<ddfreyne> They are constructed after preprocessing only
<ddfreyne> VitamineD: But reading an item attribute at preprocess itm ehsould work, yes
<VitamineD> thing is, I was chaining blog posts by storing items as attributes (of next/prev item)
<ddfreyne> VitamineD: That’s tricky… storing items/layouts as attributes is not recommended
<ddfreyne> (You can store item identifiers though)
<VitamineD> so in pry, I'd be getting mutableitemviews with @context=nil
<ddfreyne> I think nanoc should error when trying to store items/layouts
<ddfreyne> Yes
<VitamineD> and attributes rely on that context, I suppose
<ddfreyne> No (but reps do)
<ddfreyne> reps, compiled content, (raw) paths
<VitamineD> @items[] should accept identifiers, btw
<VitamineD> so I don't recall what I was doing
<ddfreyne> It does
<VitamineD> in the end I migrated to only storing identifiers.to_s
<ddfreyne> Oh, it actually only supports strings (not identifiers themselves)
<ddfreyne> Right
<VitamineD> but identifiers should not be a problem, right ?
<ddfreyne> So many bugs showing up in nanoc 4 rc2 :
<ddfreyne> :(
<VitamineD> my site compiled briefly, but I tried a scratch recompile and taht fails
<VitamineD> ArgumentError: Do not know how to convert into a Nanoc::Pattern
<VitamineD> I suppose it's getting a nil there
<ddfreyne> Where does that error occur?
<VitamineD> if only there was a debugger :p
<ddfreyne> That needs an #inspect I guess
<VitamineD> I'm calling IdentifiableCollectionView#find_all with a string coming from the metadata of my blog item
<ddfreyne> Are you sur ethat string is not nil?
<VitamineD> as I said…
<VitamineD> if only there was a debugger :p
<ddfreyne> Yeah...
<VitamineD> ah ok
<VitamineD> [4] pry(#<Blogging::Feed>)> @root
<VitamineD> => #<Nanoc::MutableItemView:0x007f8f897b5078
<VitamineD> @context=nil,
<VitamineD> @document=<Nanoc::Int::Item identifier="/notes/feed.feed">>
<VitamineD> [5] pry(#<Blogging::Feed>)> @root[:entries_pattern]
<VitamineD> => nil
<VitamineD> but that item has this: entries_pattern: /notes/[0-9][0-9][0-9][0-9]/*
<VitamineD> *facepalm*
<ddfreyne> Huh.
<VitamineD> --- # -*- mode: yaml -*-
<VitamineD> that breaks yaml I suppose
<ddfreyne> Hm, possibly
<VitamineD> that --- is nanoc or yaml ?
<ddfreyne> Both, actually ;)
<ddfreyne> But nanoc uses it to split.
<ddfreyne> I think that line makes nanoc not recognise the YAML
<VitamineD> that fails if I have a yaml comment above the first --- as well
<VitamineD> I need some refactoring to avoid storing preprocessing-time objects
<VitamineD> ok
<VitamineD> now I still have that item parent/child relationship to fix
<VitamineD> or I leave the menu as is…
VitamineD has quit [Quit: mi dormas]
VitamineD has joined #nanoc
VitamineD has quit [Ping timeout: 240 seconds]
cDlm has joined #nanoc
irsol has quit [Remote host closed the connection]
cDlm is now known as VitamineD
irsol has joined #nanoc
VitamineD has quit [Ping timeout: 264 seconds]
VitamineD has joined #nanoc