{"push_id":743023981,"size":1,"distinct_size":1,"ref":"refs/heads/normalize","head":"2ae59b5653a11ecfa7cbf235096ce6996d8de75e","before":"84890cdecc0a8c99a4266fee7cfe95455fe01d1b","commits":[{"sha":"2ae59b5653a11ecfa7cbf235096ce6996d8de75e","author":{"email":"cba4593484830aa757cb097d8d9f0ea9b692b304@boneskull.com","name":"Christopher Hiller"},"message":"normalize names, encoding information & writeHead; closes #71 and #73\n\n- Add `capitalize` package as dependency\n- To normalize option names, capitalize each word of the name.  \"content-format\" becomes \"Content-Format\", etc.  special case for \"ETag\", which was added to the alias map.\n- Fixed an undefined variable in `option_converter`'s `contentFormatToBinary()`\n- Added `OutgoingMessage.prototype.writeHead()` as to provide more compatibility with the `http` module\n- Encoding information can be sent in *any* `Content-Format` value, but it is discarded.  From what I can gather from the RFC7252 and other RFCs I read, we only seem to be *required* to accept the encoding information with `text/plain`; support any other format would be optional, but since sending a type such as `application/json; charset=utf-8` is so common, we may as well\n- Updated `README.md` with `writeHead()` info.","distinct":true,"url":"https://api.github.com/repos/boneskull/node-coap/commits/2ae59b5653a11ecfa7cbf235096ce6996d8de75e"}]}