while reading the websockets PR, I noticed the spec namespaces, that I liked
BUT, they feel wired.
While io.pedestal.http uses the :io.pedestal.http/port keyword to specify the port number, the https://github.com/pedestal/pedestal/blob/master/service/src/io/pedestal/http/specs.clj#L47 namespace actually specify :io.pedestal.http.spec/port keyword.
Other libraries like https://github.com/seancorfield/next-jdbc/blob/develop/src/next/jdbc/specs.clj in fact use the .spec namespaces to define the keyword, but as it use -un qualified keywords, it is not wrong.
That sounds like a bug. I must have been sloppy moving the specs out to their own namespace.
Should have been caught by tests.
Yep, tests were not instrumenting at the right time to catch these.
Working on the fix.