Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
framework.Object needs a better name
See original GitHub issueCalling a type Object, even within a namespace, is bound to cause confusion. (Sidebar - “framework” is not an effective namespace). Colliding with object will alienate experienced programmers and will cause beginners to become trapped.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Names of Type Members - Framework Design Guidelines
Learn the guidelines for naming type members in .NET, such as methods, properties, events, and fields.
Read more >Naming Conventions: Why You Need Them for Clean Data
In this lesson, we'll go over why you need a naming standard and our preferred approach, the object-action framework.
Read more >Object Framework — Flow Framework dev-master ...
Object Names vs. We first need to introduce some namings: A class name is the name of a PHP class, while an object...
Read more >Top 10 Most Common Spring Framework Mistakes
Java's open source Spring framework is a popular tool for creating high performing applications using plain old Java objects, but as with any...
Read more >c# - Copy Entity Framework Object
You need to make correct deep copy of the whole entity graph - the best way is to serialize the original entity graph...
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 Free
Top 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
Please reconsider. Any of the alternatives would be better than this. “Object” will clash with every programmer’s mental model.
Closing the issue now prioritises the team over downstream developers.
Fair point!