-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Annotate serialization #8
Comments
Looking at our tooling, this is likely to be most easily achieved by keeping a history of serialization docfx, even if we don't publish documentation for individual versions. We'll probably need to make the tooling itself slightly more flexible (e.g. specifying a single package per run) as there's quite a lot of hard-coded information in there at the moment. |
jskeet
added a commit
to jskeet/nodatime.org
that referenced
this issue
Apr 16, 2019
- Reorganize the history branch to be per-project - Rewrite scripts and tools to cope with that Still TBD: - Reinstate CheckMembers in DocfxAnnotationGenerator, but only for unstable - Sort the TOC to avoid NodaTime.Testing going at the bottom (I'll create issues for those.) Fixes nodatime#8
jskeet
added a commit
that referenced
this issue
Apr 16, 2019
- Reorganize the history branch to be per-project - Rewrite scripts and tools to cope with that Still TBD: - Reinstate CheckMembers in DocfxAnnotationGenerator, but only for unstable - Sort the TOC to avoid NodaTime.Testing going at the bottom (I'll create issues for those.) Fixes #8
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice to be able to see what version each member appeared in for serialization
The text was updated successfully, but these errors were encountered: