summaryrefslogtreecommitdiffstats
path: root/spec/unit/parser
Commit message (Collapse)AuthorAgeFilesLines
...
* Changing some methods in the Compile class toLuke Kanies2008-02-112-25/+25
| | | | | be more internally consistent (switched store_resource to add_resource, and store_override to add_override).
* Fixed #1030 - class and definition evaluation has been significantlyLuke Kanies2008-02-112-113/+224
| | | | | | refactored, fixing this problem and making the whole interplay between the classes, definitions, and nodes, and the Compile class much cleaner.
* Converting the Compile class to use a Node::Catalog instanceLuke Kanies2008-02-111-30/+13
| | | | | as its resource container, instead of having its own behaviour around resource uniqueness.
* Moving all of the tests for Puppet::Parser::Compile toLuke Kanies2008-02-111-31/+333
| | | | | | rspec, so I can refactor the class to more heavily rely on a Node::Catalog instead of doing its own resource container management.
* More AST refactoring -- each of the code wrapping classesLuke Kanies2008-02-082-4/+4
| | | | | | | | | | | just returns a resource from its evaluate() method, and all of the work is done in the evaluate_code method. This makes the code cleaner, because it means 1) evaluate() has the same prototype as all of the other AST classes, 2) evaluate() is no longer called indirectly through the Parser Resource class, and 3) the classes themselves are responsible for creating the resources, rather than it being done in the Compile class.
* Refactoring the AST classes just a bit. I realized thatLuke Kanies2008-02-082-6/+6
| | | | | | all of the evaluate() methods only ever accepted a scope, and sometimes one other option, so I switched them all to use named arguments instead of a hash.
* Significantly refactoring the lexer, including adding Token and TokenListLuke Kanies2008-01-301-0/+465
| | | | | | classes for managing how the tokens work. I also moved they tests to RSpec, but I didn't rewrite all of them.
* Fixing #976 -- both the full name of qualified classes andLuke Kanies2008-01-191-0/+60
| | | | | | the class parts are now added as tags. I've also created a Tagging module that we should push throughout the rest of the system that uses tags.
* Fixing #971 -- classes can once again be included multipleLuke Kanies2008-01-071-1/+14
| | | | times.
* Fixing #967 -- relationships now work when running 0.23.x clientsLuke Kanies2007-12-181-2/+7
| | | | against 0.24.0 servers.
* This should be the last fix for exported resources.Luke Kanies2007-12-111-0/+21
| | | | | | Hosts were keeping the export bit on all resources, even when they'd collected another host's resources, which caused a duplicate copy that was still exported.
* Renaming 'configuration' to 'catalog', fixing #954.Luke Kanies2007-12-112-14/+14
|
* Fixing #923. Resources that are collected on the localLuke Kanies2007-12-061-13/+0
| | | | host are no longer marked as not exported.
* Theoretically, this patch is to fix #917 (which it does), butLuke Kanies2007-11-282-33/+42
| | | | | | | | | | | | | | | | | | | there were enough problems fixing it that I decided something more drastic needed to be done. This uses the new Puppet::ResourceReference class to canonize what a resource reference looks like and how to retrieve resources via their references. Specifically, it guarantees that resource types are always capitalized, even when they include '::' in them. While many files are modified in this commit, the majority of changes are quite small, and most of the changes are fixing the tests to use capitalized types. As we look at consolidating some of our resource types, we could consolidate the ResourceReference stuff at the same time, but at least the Puppet::Parser::ResourceReference class subclasses the main Puppet::ResourceReference class.
* Fixing #921, mostly by just deleting the existing test. I hadLuke Kanies2007-11-261-4/+22
| | | | | | already migrated all of the tests into rspec but forgot about these tests -- they were only in the rails/ subdir because people kept not running the parser/ tests after modifying the Rails code.
* Incorporating patch ↵Luke Kanies2007-11-241-0/+386
| | | | | | | | | | 20071030034736-6856b-6004090b3968cdbf7d366a03ee1c44e2160a3fe0.patch from womble, and rewriting and significantly enhancing the unit tests for the Puppet::Parser::Collector class; it should have full coverage now. There are no integration tests for it, so there's still no guarantee that it works at all, but hey, we're a lot better off than we were.
* Fixing the first part of #787. Not all collections wereLuke Kanies2007-11-201-0/+25
| | | | | | | | being evaluated on the first pass because they were being deleted from the collections list during evaluation, which caused some to get skipped. This commit fixes that problem, which helps in the trivial cases where the collections are in the same scope. I expect it's still broken for more complicated usages.
* Fixing #446. I ended up largely not using porridge's patch,Luke Kanies2007-11-191-0/+50
| | | | | | but only because the code (and my coding style, to some extent) has changed so much in the last few months. Also, added specs.
* Moving some compile tests to the spec/ directory, andLuke Kanies2007-11-121-0/+100
| | | | | | | | | | | | switching the node scope to no longer be lazy evaluation, just like I switched 'main'. When I made all of these classes and nodes lazy evaluated, I should have decoupled my real goal (using resources to evaluate them) from the idea of lazy-evaluating them, and this basically does that. I also changed the scope heirarchy slightly so that scopes will tend to be below the node scope, altho this was already generally the case.
* Switching the class resource evaluation to only happenLuke Kanies2007-11-081-6/+12
| | | | | when using :include, not (for example) when evaluating node classes.
* Classes once again get evaluated immediately when theLuke Kanies2007-11-081-12/+87
| | | | | | | | | | 'include' function is used, instead of being lazy-evaluated. Previous work caused resources to get created to model these classes, but in the process, I removed the fact that the classes were evaluated immediately. This meant that you couldn't guarantee that a class was evaluated before you went to use its variables.
* Adding this test stub that's been sittingLuke Kanies2007-10-181-0/+47
| | | | around in my repository for a while.
* Adding a :code setting for specifying code to runLuke Kanies2007-10-051-37/+7
| | | | | | | | instead of a manifest, and removing all of the ambiguity around whether an interpreter gets its own file specified or uses the central setting. Most of the changes are around fixing existing tests to use this new system.
* This commit is focused on getting the 'puppet' executableLuke Kanies2007-10-052-21/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | to work. As a result, it involves a lot of integration-level testing, and a lot of small design changes to make the code actually work. In particular, indirections can now have default termini, so that configurations and facts default to their code terminus Also, I've removed the ability to manually control whether ast nodes are used. I might need to add it back in later, but if so it will be in the form of a global setting, rather than the previous system of passing it through 10 different classes. Instead, the parser detects whether there are AST nodes defined and requires them if so or ignores them if not. About 75 tests are still failing in the main set of tests, but it's going to be a long slog to get them working -- there are significant design issues around them, as most of the failures are a result of tests trying to emulate both the client and server sides of a connection, which normally would have different fact termini but in this case must have the same terminus just because they're in the same process and are global. The next step, then, is to figure that process out, thus finding a way to make this all work.
* Fixing #814 -- when files are missing, the exceptions shouldLuke Kanies2007-10-031-24/+27
| | | | now be more reasonable.
* Renaming the 'Puppet::Util::Config' class toLuke Kanies2007-09-221-2/+2
| | | | | | | 'Puppet::Util::Settings'. This is to clear up confusion caused by the fact that we now have a 'Configuration' class to model host configurations, or any set of resources as a "configuration".
* Fixing #807. The exception handling should more closely resemble how it ↵Luke Kanies2007-09-061-2/+4
| | | | used to be done.
* Flipped the switch so that compiles now return a Configuration instance ↵Luke Kanies2007-09-041-8/+12
| | | | instead of pre-extracting the configuration.
* Doing a small amount of refactoring, toward being able to use Parser ↵Luke Kanies2007-09-032-0/+105
| | | | resources to evaluate classes and nodes, not just definitions. This will hopefully simplify some of the parsing work, and it will enable the use of a Configuration object that more completely models a configuration.
* Deleting old documentation that somehow made it back into the tree in the ↵Luke Kanies2007-09-011-0/+48
| | | | switch to git, and refactoring the evaluate_classes method on the compile object so I can use resources as intermediaries, thus making classes do late-binding evaluation.
* Multiple environment support now works, and I have even tested it in real ↵Luke Kanies2007-08-261-25/+47
| | | | life. This commit is mostly a bug-fix commit, resulting from the difference between real-life testing and unit testing.
* Removing this test for now; I do not have time to port it from test/unit to ↵Luke Kanies2007-08-251-755/+0
| | | | rspec
* Renaming the "configuration" object to "compile", because it is only a ↵Luke Kanies2007-08-251-0/+755
| | | | transitional object and I want the real "configuration" object to be the thing that I pass from the server to the client; it will be a subclass of GRATR::Digraph.
* Everything up to the parser (and the Modules) is ready to support multiple ↵Luke Kanies2007-08-231-0/+76
| | | | environments, including the parser having an environment setting. I have also created my first spec-based tests, for the interpreter (and deleted the old test/unit tests).
* Building a stand-alone spec directory for creating the new spec-based tests.Luke Kanies2007-08-231-0/+94
generated by cgit (git 2.34.1) at 2026-01-24 10:20:53 +0000