{"push_id":987830781,"size":6,"distinct_size":6,"ref":"refs/heads/master","head":"0a5ccff514070a004fd61d0c150949a3d42886b5","before":"9075a226c1751f20106d570bd8cc923718cad53d","commits":[{"sha":"8fc2c77795b4649bf9cad0344eb32e58663c4876","author":{"email":"739a1fa7d929e3536c162fdbee2b69427ae2ee08@gmail.com","name":"Zahari"},"message":"Implement element_of decorator\n\nThis allows to parse a list if we already know how to parse an element\nof the list.\n\nJust write\n\n@element_of(\"list_key\")\ndef parese_listelem(elem):\n    ...\n\nThis will be used to automatize outer loops.","distinct":true,"url":"https://api.github.com/repos/Zaharid/reportengine/commits/8fc2c77795b4649bf9cad0344eb32e58663c4876"},{"sha":"366e15dda6645390d98f46dbce3a34b85762f285","author":{"email":"739a1fa7d929e3536c162fdbee2b69427ae2ee08@gmail.com","name":"Zahari"},"message":"Use DAG in reportengine\n\nThis allows to parse an element based on the value of other elements.\nIn an ideal world this wouldn't be necessary, but configuration files\nget quite tricky in real life.","distinct":true,"url":"https://api.github.com/repos/Zaharid/reportengine/commits/366e15dda6645390d98f46dbce3a34b85762f285"},{"sha":"7d7f230369bdf714cb633a88ce2413982dd92693","author":{"email":"739a1fa7d929e3536c162fdbee2b69427ae2ee08@gmail.com","name":"Zahari"},"message":"Improve error reporting in config\n\nProperly init the error, and raise on bad yaml parsing.","distinct":true,"url":"https://api.github.com/repos/Zaharid/reportengine/commits/7d7f230369bdf714cb633a88ce2413982dd92693"},{"sha":"9714bf1b6b72790582424e42bdd2edbd9b9961ac","author":{"email":"739a1fa7d929e3536c162fdbee2b69427ae2ee08@gmail.com","name":"Zahari"},"message":"Implement NS resolver\n\nWe change the paradigm, from having one namespace in total, to one\nnamespace per node.\n\nWith this several limitations of the current approach will be overcame\ntrivially (at the expense of more work).\n\nThe namespace where each node is to write is encoded in a namespace\nspecification (nsspec) so as to stack dictionaries, lists or elements\nof lists within a given root dictionary (somehow initiated by the\nconfig). In such a way, every complex element of the config can span\na namespace if required. The rules are:\n\n - Start with the keys of the root dictionary.\n - Specify the next element, which can be:\n    * A dictionary: The keys of the inner dict are available as symbols, and if no key\n      found, those of the outer).\n    * A list: If the list elements are dictionaries, a namespace is\n      spanned for each.\n    * An element of a list: Does what you expect.\n\nThis commit breaks resourcebuilder, which will be heeavily modified.","distinct":true,"url":"https://api.github.com/repos/Zaharid/reportengine/commits/9714bf1b6b72790582424e42bdd2edbd9b9961ac"},{"sha":"dc6206e492e9428825d0d6fbf39770392de59733","author":{"email":"739a1fa7d929e3536c162fdbee2b69427ae2ee08@gmail.com","name":"Zahari"},"message":"Make parse functions check type themselves\n\nThis makes the interface more pleasant to use, and allows to add\nmetadata to the funcs and then retrieve them with get_parse_func.","distinct":true,"url":"https://api.github.com/repos/Zaharid/reportengine/commits/dc6206e492e9428825d0d6fbf39770392de59733"},{"sha":"0a5ccff514070a004fd61d0c150949a3d42886b5","author":{"email":"739a1fa7d929e3536c162fdbee2b69427ae2ee08@gmail.com","name":"Zahari"},"message":"Add support for named_element_of\n\nThis will be useful eventually, to allow nested parsers.","distinct":true,"url":"https://api.github.com/repos/Zaharid/reportengine/commits/0a5ccff514070a004fd61d0c150949a3d42886b5"}]}