-
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
Namespace docs not being used #12
Comments
We could try using overwrite files for this. We may need to modify the templates, too. |
jskeet
added a commit
to jskeet/nodatime.org
that referenced
this issue
Apr 10, 2019
We can now remove NamespaceDoc.cs files from the other repos. Fixes nodatime#12
jskeet
added a commit
to jskeet/nodatime.org
that referenced
this issue
Apr 10, 2019
We can now remove NamespaceDoc.cs files from the other repos. Fixes nodatime#12
jskeet
added a commit
that referenced
this issue
Apr 10, 2019
We can now remove NamespaceDoc.cs files from the other repos. Fixes #12
jskeet
added a commit
that referenced
this issue
Apr 13, 2019
We can now remove NamespaceDoc.cs files from the other repos. Fixes #12
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have classes called
NamespaceDoc
for documentation purposes. Sandcastle used to recognize this; docfx doesn't (yet). There's an issue here for it: dotnet/docfx#952We should keep track of what docfx is doing and respond appropriately.
The text was updated successfully, but these errors were encountered: