dotnet: consider emitting namespace, class, method, and field/property names referenced by an assembly
See original GitHub issue(1) e.g. emit the following for System.IO.File::OpenRead
:
- namespace: System.IO
- class: File
- method: OpenRead
(2) be more explicit to avoid FPs resulting from naming conflicts, e.g.:
- namespace: System.IO
- class: System.IO.File
- method: System.IO.File::OpenRead
and for properties, e.g. (more discussion in #939):
- namespace: System.Net
- class: System.Net.WebRequest
- property: System.Net.WebRequest::Method
I like option 2 the best, and I think this would apply to both file and function scopes and both internal and external references.
Issue Analytics
- State:
- Created a year ago
- Comments:8
Top Results From Across the Web
Namespace and class with the same name? - Stack Overflow
I don't recommend you to name a class like its namespace, see this article. The Framework Design Guidelines say in section 3.4 “do...
Read more >Organizing types in namespaces | Microsoft Learn
NET uses namespaces to organize its many classes, as follows: ... the scope of class and method names in larger programming projects.
Read more >Static classes with identical names and namespaces into ...
Create library Project A and add a static class with some methods ... 'string' could be found (are you missing a using directive...
Read more >Config File Reference - Dotfuscator Professional 6.5
The exclusion list has support for excluding names by type, method, field, property, event, assembly, module, or namespace. Each type of rule is...
Read more >Google C++ Style Guide
Comment Style; File Comments; Class Comments; Function Comments ... Namespaces should have unique names based on the project name, and possibly its path....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah, yeah, that could be neat to detect on namespaces. For simplicity I’d then say we emit namespace, class, method, and property/field names for all classes?!
see #939 for property access. #1030 covers namespace/class/method.