|
|
820abe2bef
|
LocationSolver: provide DSL notation to write "create clauses"
|
2018-02-11 04:00:59 +01:00 |
|
|
|
7a167c4c3a
|
LocationSolver: draft pattern for writing those test cases
...which shows: we also need a DSL mechanism for writing "create clauses"
|
2018-02-11 02:34:56 +01:00 |
|
|
|
65a86bc426
|
LocationSolver: define extensive test coverage to be written (#1127)
|
2018-02-10 02:03:09 +01:00 |
|
|
|
6d0e8a35a6
|
LocationSolver: simple unit test PASS
|
2018-02-10 00:34:24 +01:00 |
|
|
|
bf314482da
|
LocationSolver: draft the simple usage scenario (unit test) (#1127)
|
2018-02-08 00:37:02 +01:00 |
|
|
|
10d2cafba9
|
LocationSolver: draft entities involved in location solving (#1127)
basically this will be built on top of the path matching / resolving mechanism coded thus far.
but we'll need some additional flags and some DSL magic
|
2018-02-07 04:03:39 +01:00 |
|
|
|
136e78d023
|
DockAccess: decide on next steps towards integration (#1126)
|
2018-02-01 23:08:43 +01:00 |
|
