coryodaniel / k8s_client / 15

56%

master: 77%

push

travis-ci

Partially implemented client w/o macros for routing.

This falls apart once you get to different scoping of resources.

It currently works, because the macro is agnostic about opts being
passed into the match. If it gets too much, interpolation doesnt find
anything to do with the param and moves on, if its missing params, it
returns an error with the param (at runtime) that it knows its missing.

In this approach, the route_map has the params built into the map, so
you have to know which params are required ahead of time.

You can feel this in the awkwardness of having to pass in `attrs[]`
individually to `path_for`.

Could probably resolve this by taking attrs as a whole, and internal to
path_for removing attr's from the list that are nil, so that it can find
the right path if too much is passed in.

For example, if a resource map is destructured into path args and its a
cluster scoped resource, `namespace` ends up being 'nil` in the opts
list. Since the keys in this list are used to find the path, it tries to
find a namespaced path for a cluster scoped resource.

36 of 36 new or added lines in 3 files covered. (100.0%)

86 of 178 relevant lines covered (48.31%)

43.58 hits per line