Andreas Öhlund
Andreas Öhlund
Side note: We use apiapprover for most of our projects so any changes to the public api is visible in pull requests if you know what to look for https://github.com/JakeGinnivan/ApiApprover...
Wouldn't chocolatey be more appropriate since its an "app" ?
Fair enough, not having to bother with the approval mess that comes with chocolatey would be a win
Here is another example where it would be better to hightlight the breaking changes http://apicomparer.particular.net/compare/EntityFramework/6.0.0...6.1.3 and yes EF didn't follow semver here :)
On thing to note is that pulling down the nugets and creating the diff can take a few seconds the first time. The current site is polling until it gets...
Agree with @richorama , lets go simple first?
I do see your point @danielmarbach How about we do this. ### Case 1 - Results already available Since we cache the generated diffs we can just send them back...
Agreed, good points regarding the caching. Side note: we actually render the results as html and stores it so its cheap to return them again. We would do the same...
Should we go with some tabs ala http://designscrazed.org/html5-css3-accordion-tabs/ ?
and also project.json files?