Closed kevinkreiser closed 3 years ago
Another side question I have is, should we add some semver to the API? I've been changing the main methods here and there and whenever you make your next release I suppose the version should reflect that. I think having the version number in code might be helpful to others as well.
If we break the API, I'll bump the release version to the next major, so 2.0.0
.
@vthiery thanks for all the review feedback i'll get them all changed and break out the other stuff into another PR. should have that doen shortly!
i believe ive removed all of the additional changes here and have down to just the changes discussed in the first round of review:
@vthiery i got master merged in with the linting PR, i think this is ready for review again
@vthiery OK I feel pretty sure now that I've covered all of the things discussed in the review comments. Sorry for taking such a long time on that one!
fixes #18
This PR expands the test application that we run in CI so that it spawns a thread which listens on the statsd UDP port and stores the messages it got in memory. Then we validate that the messages it received were the ones we expected it to.
I made quite a couple changes here to make this more testable:
There were other changes I made as nice-to-haves:
TODO
s as questions in the code or suggestions, please let me know which ones i should implement or removeAnother side question I have is, should we add some semver to the API? I've been changing the main methods here and there and whenever you make your next release I suppose the version should reflect that. I think having the version number in code might be helpful to others as well.