Some methods in Nanoc are not meant to be overridden. Some classes are not supposed to be subclassed either.
There’s no good way to prevent this in Ruby (there’s e.g. no “final” keyword, like in Java), but perhaps Nanoc can do something to prevent bugs that occur in sites where some final classes/methods are overridden.
Some methods in Nanoc are not meant to be overridden. Some classes are not supposed to be subclassed either.
There’s no good way to prevent this in Ruby (there’s e.g. no “final” keyword, like in Java), but perhaps Nanoc can do something to prevent bugs that occur in sites where some final classes/methods are overridden.
cfr nanoc/nanoc/issues/1148