Last 12 weeks · 0 commits
2 of 6 standards met
I actually encountered this issue when using confd (which depends on this) with etcd as a backend. Since etcd flattens directories, you can end up with a number of keys that are a section of a potentially deeper path. The behavior I was expecting was based off the etcd documentation for since I couldnt find anything in this repo, so hopefully this is correct: Returns all subkeys, []string, where path matches its argument. Returns an empty list if path is not found. Given the keys (like how etcd would structure them): Before this change, if I tried to list all of the keys in the directory, I would get a list with two items - when I would expect the output to be: as they are located in the path. Example program I used to test this change:
Repository: kelseyhightower/memkv. Description: Simple in-memory key/value store backed by a map Stars: 56, Forks: 25. Primary language: Go. Languages: Go (100%). License: MIT. Latest release: v0.1.1 (8y ago). Open PRs: 1, open issues: 0. Last activity: 7y ago. Community health: 42%. Top contributors: kelseyhightower, jjjordanmsft, okushchenko, sukrit007, thorduri, wuranbo.