| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
constraintErrorMessage.
|
|
|
|
where one contains another (starting with the first element).
|
|
|
|
a tree.
|
|
Making it linear time at cost of knowing the data for all path elements
was probably a bad idea.
|
|
It now lives in a Util, a module that implements the adopter design pattern.
|
|
Looks like it was a bad idea.
This reverts commit 7c02dc2a949798a3fea3dbcce5a63888a3f10f51.
|
|
|
|
Rename helpString to just help.
|
|
Make order of elements unimportant.
Remove unused references.
|
|
Make extends an attribute. Remove nodeList tag.
|
|
|
|
1. Don't distinguish name and value constraints, they
have exact same structure.
2. Don't use individual error messages for all constraints.
If they work like OR, it makes little sense.
3. Move most of data from arguments to tag bodies.
|
|
|
|
|
|
for multilevel insert.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
insert remains a special case, maybe it can fit it in it if we pass
to functions instead of one (one for "found" and another one for "not found").
|
|
|
|
|
|
|
|
|
|
They will be used in node reordering.
|
|
|
|
|
|
|
|
everywhere.
|
|
|
|
|
|
|
|
It's not like there's anything else we can insert or delete.
|
|
|
|
Splitting directories was a bit premature and unnecessary.
|
|
|
