{"shas":[["e9ee621e1f32a984ca4b18e814e7f3549612dcc5","9956a36b5e6e3cca7ae8066f76f964d5f08c7b1e@gmail.com","(6130) Change header level on metaparameter reference\n\nIndividual metaparameters under the main H2 on the page should be H3s, not H4s.","nfagerlund"],["637e139556d7a0fa37d9e7626cfedb23430177d6","9956a36b5e6e3cca7ae8066f76f964d5f08c7b1e@gmail.com","(#6270) Fix formatting in regsubst function's doc string\n\n* Fixed ULs being interpreted as code blocks\n* Changed an example for variety.\n* Turned set of paragraphs inside a LI into a nested list.","nfagerlund"],["0b7faa6c95dbb734019a6e659b838ef24103571a","9956a36b5e6e3cca7ae8066f76f964d5f08c7b1e@gmail.com","(#6270) Fix formatting in split function's doc string\n\n* Repaired a 2-indent/4-indent issue that kept a code block from being recognized\n* Wrapped literal strings in backticks to format as code and protect from Markdown\n* Added note about backslashes for escaping metacharacters.","nfagerlund"],["781601f8e7a9c6aecc5c9de66b1597b1879450d2","9956a36b5e6e3cca7ae8066f76f964d5f08c7b1e@gmail.com","Merge branch 'ticket/2.6.next/6270' into 2.6.next","nfagerlund"],["48bc7d00ca87fa92cdde0b993529bba3827fa47e","c9103f7e92504f8408c832361c569d2cccc6caad@daysofwonder.com","Fix #6280 - puppetdoc crashing on string interpolation\n\nThe following manifest was crashing puppetdoc:\n  class test {\n     include \"test::$operatingsystem\"\n  }\n\nBecause the quoted string is \"rendered\" as a concat AST, which in turn\nended being an array when entering RDoc.\n\nSigned-off-by: Brice Figureau <brice-puppet@daysofwonder.com>","Brice Figureau"],["cfa0c32fc5149464af97235a7bb458950d19cc82","c9103f7e92504f8408c832361c569d2cccc6caad@daysofwonder.com","Fix #6281 - Make sure puppetdoc analyzes all files\n\nIt can happen that when parsing a file puppet parses other manifests\nif they get imported (this is at least true for site.pp, even in\nignoreimport=true). Thus those files are now \"watched\".\nBut puppetdoc needs to analyze all files, and since 99c101 we are now\nchecking if the file was already parsed to not reparse it again.\nIf that was the case, though, we weren't analyzing the produced code.\nThus it was possible to not produce documentation for the site.pp content.\n\nSigned-off-by: Brice Figureau <brice-puppet@daysofwonder.com>","Brice Figureau"],["b4a171e78c501208798220910352943331ceb9e0","c9103f7e92504f8408c832361c569d2cccc6caad@daysofwonder.com","Fix #5720 - puppetdoc misses some class comments\n\nIt appears that the fix for #5252 wasn't complete, and class, nodes and\ndefinition were still using the current lexer line number instead of\nthe line number of the class/define/node token.\nThis combined with some missing comments stack pushing/pop on parenthesis\nprevented puppetdoc to correctly get the documentation of some class (including\nparametrized ones).\n\nSigned-off-by: Brice Figureau <brice-puppet@daysofwonder.com>","Brice Figureau"],["90905073a6e1136c80cd59dca1a9594f4a859126","c9103f7e92504f8408c832361c569d2cccc6caad@daysofwonder.com","Fix #6267 - puppetdoc embedded links to puppet entities are not hyperlinked\n\nPuppetdoc was relying on RDoc to provide the puppet entity (class, definition\nnode, etc...) hyperlinking in comments.\nUnfortunately, RDoc was assuming namespaces are capitalized like Ruby\nnamespaces and that definition would use the # or . separator.\n\nThis change adds on top of RDoc puppet namespace format for classes and\ndefinition.\n\nThis will make sure the comment hyperlinking will work as intented.\n\nSigned-off-by: Brice Figureau <brice-puppet@daysofwonder.com>","Brice Figureau"],["c373b6272ddd4daabf15d1b459ef3e86072e3f26","c9103f7e92504f8408c832361c569d2cccc6caad@daysofwonder.com","Fix #6269 - Hashes only work with two levels of access\n\nThe following manifest was failing:\n  $hash = { 'a' => { 'b' => { 'c' => 'it works' } } }\n  $out = $hash['a']['b']['c']\n\nbecause of a typo in the grammar.\n\nSigned-off-by: Brice Figureau <brice-puppet@daysofwonder.com>","Brice Figureau"],["414e3a5989c4c1010af0c5d3f61af2608d91d9b8","c9103f7e92504f8408c832361c569d2cccc6caad@daysofwonder.com","Fix #5516 - Hashes can't be used in selectors\n\nThe following manifest was producing a parse error:\n$int = { 'eth0' => 'bla' }\n$foo = $int['eth0'] ? {\n  'bla' => 'foo',\n   default => 'bleh'\n}\n\nbecause selectors didn't support hash access.\n\nSigned-off-by: Brice Figureau <brice-puppet@daysofwonder.com>","Brice Figureau"],["1abfd9c2e550be8cebdd94629d0f9759f14f7f34","3d0f3b9ddcacec30c4008c5e030e6c13a478cb4f@puppetlabs.com","Merge branch 'masterzen/tickets/2.6/5720' into bug/2.6.next/5720-puppetdoc-fails-on-parameterized-class","Daniel Pittman"],["b5b5923bf41196f5e72a69bfa627120c75732fe5","3d0f3b9ddcacec30c4008c5e030e6c13a478cb4f@rimspace.net","misc: ast_context has two arguments, not one.\n\nThis updates the spec expectation to reflect that, eliminating a warning\nduring the spec run.","Daniel Pittman"],["16e79f075622aa155a112d5a271c386f4ebc0241","3d0f3b9ddcacec30c4008c5e030e6c13a478cb4f@puppetlabs.com","Merge branch 'bug/2.6.next/5720-puppetdoc-fails-on-parameterized-class' into 2.6.next","Daniel Pittman"],["e512e3effa134271564177e095c6afc19bebe62f","3d0f3b9ddcacec30c4008c5e030e6c13a478cb4f@rimspace.net","(#5977) fix spec test failure when new applications are introduced.\n\nThe test here was previously fragile, in that it would break when new\napplications were introduced, and in that it depended on the order of items\nreturned from reading the directories on disk.\n\nIt is now insensitive to those changes, and still verifies that the results we\nrequire occur, reducing long term maintenance cost.\n\nReviewed-by: James Turnbull <james@puppetlabs.com>","Daniel Pittman"],["d9b168b00a7c86489d8b1cf7c28d4e37205710f7","3d0f3b9ddcacec30c4008c5e030e6c13a478cb4f@puppetlabs.com","Merge branch 'masterzen/tickets/2.6.x/5516' into bug/2.6.next/5516-hashes-can't-be-used-in-selectors","Daniel Pittman"],["5c26f6828e0e2c1370966472d4d62b2e001c9f0b","3d0f3b9ddcacec30c4008c5e030e6c13a478cb4f@rimspace.net","(#5516) Rebuild parser.rb after merge.\n\nThe automatically generated parser.rb needed to be rebuilt to make the syntax\nchanges functional; this commits only that rebuild.","Daniel Pittman"],["98f79dc2e44502bf781dbce180762b892859d4e1","3d0f3b9ddcacec30c4008c5e030e6c13a478cb4f@puppetlabs.com","Merge branch 'bug/2.6.next/5516-hashes-can't-be-used-in-selectors' into 2.6.next","Daniel Pittman"],["a0d320439c72f7b7969cd51b33a8db141eb9a599","3d0f3b9ddcacec30c4008c5e030e6c13a478cb4f@rimspace.net","(Fixes #6269) merge changes from masterzen that resolve the issue.\n\nparser.rb manually rebuilt to resolve global grammer chances.","Daniel Pittman"],["9bd15b77d4cc210249228ff628b6e7708124aca3","3d0f3b9ddcacec30c4008c5e030e6c13a478cb4f@puppetlabs.com","Merge branch 'bug/2.6.next/6269-hashes-only-work-with-two-levels' into 2.6.next","Daniel Pittman"],["193016dd152ff17ba94867897656ddca41621b3e","3d0f3b9ddcacec30c4008c5e030e6c13a478cb4f@rimspace.net","(#5977) fix spec test failure when new applications are introduced.\n\nThe test here was previously fragile, in that it would break when new\napplications were introduced, and in that it depended on the order of items\nreturned from reading the directories on disk.\n\nIt is now insensitive to those changes, and still verifies that the results we\nrequire occur, reducing long term maintenance cost.\n\nReviewed-by: James Turnbull <james@puppetlabs.com>","Daniel Pittman"]],"repo":"jhelwig/puppet","actor":"jhelwig","ref":"refs/heads/2.6.next","size":135,"head":"4a8c631a5f909c3e482e087f88cf618e1b44ee4e","actor_gravatar":"2268f1752ed1f002b0f100f964ce49d5","push_id":26294788}