Comments (8)
Hi, I totally agree, the documentation should not leak. I will look into this.
Iām thinking about a potential middle ground right now which might allow to preserve the XML documentation during development: The XML doc could simply be wrapped in an #if DEBUG
block. Then it would be visible during development, but would not appear in a release build (which should be used for every published library). Would this satisfy your use case?
And thanks for raising the issue! Much appreciated!
from nullable.
Looks like a good idea to me. Thanks for your quick answer!
If you don't have time to implement the change I can make a PR in a few hours.
from nullable.
I should be able to make the change today when I arrive at home, but thanks for the offer!
I will notify you when it is done.
from nullable.
I just uploaded the new version 1.2.1 which should fix the issue as discussed. In DEBUG builds, the XML documentation is still there for convenient development, but in RELEASE builds, it will be omitted and therefore not leak.
I have done my best to test the new version locally with a variety of project types, but I cannot cover every single kind of setup. Please feel free to tell me if the issue persists despite the changes.
from nullable.
I can confirm that the issue has been resolved. Thanks!
from nullable.
Not to mention automatically-generated online docs!
What doc generator are you using that produces documentation for internal types from your xml file?
from nullable.
What doc generator are you using that produces documentation for internal types from your xml file?
Point taken. My main concern, however, was with the extra XML in all NuGet packages for my .NET Standard 2.0 libraries. It just shouldn't have been there. As for doc generators, I may have been mistaken.
from nullable.
There's probably a lot of xml documentation for internal types in that file for any library that bothers to document itself. I've never heard a complaint myself. And this is just a small amount, I can't imagine why it would matter.
But the work is done to suppress it already, so water under the bridge.
from nullable.
Related Issues (15)
- [Discussion] Installation Error when using NuGet's packages.config file HOT 14
- Use #pragma warning restore instead of #pragma warning enable HOT 1
- [Solution] Nullable attributes are not discovered in WPF projects HOT 7
- Internal attributes prevent build on .NET4.8 HOT 5
- Incremental build is slowed by timestamps of generated source file HOT 14
- Automatically exclude attributes from style/code analysis HOT 1
- Why are the attributes marked as internal? HOT 8
- Reference problem in WPF environment HOT 3
- Can't build on older targets without explicit LangVersion HOT 3
- Can you add package to support InAttribute for netstandard1.0 as target HOT 1
- CS0246 build errors on .NET 6.0.300 SDK HOT 8
- Support for netstd < 2.0 HOT 6
- Other ways to support exclude from code analysis? HOT 3
- Add support for [MemberNotNull] and [MemberNotNullWhen] HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
š Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ššš
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ā¤ļø Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nullable.