[MemberExpression] Long object access doesn't wrap
See original GitHub issueNot sure if this is a bug or just a rare enough case that it doesn’t matter
Input
something()
.something
.something()
.something
.something()
.something
.something()
Output
something().something.something().something.something().something.something();
(Longer than 60 chars)
Input
someVeryLongMethodObjectName
.withSomeVeryLongObjectKey
.andAnotherLongKey;
Output
someVeryLongMethodObjectName.withSomeVeryLongObjectKey.andAnotherLongKey;
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
c# - Access the value of a member expression - Stack Overflow
Update I have tried this but it doesn't seem to work. var memberExpression = (MemberExpression)GetRootConstantExpression(m); var fi = (PropertyInfo) ...
Read more >Optional Chaining Bugs Checklist #7256 - babel/babel - GitHub
If a plugin transforms MemberExpression nodes and doesn't know to expect optional as a ... true - This node is explicitly an optional...
Read more >Working with Expression Trees in C# • Oleksii Holub
In order to do that, we have to create an entry point by wrapping everything in a lambda expression. To turn it into...
Read more >Determining the object that caused a null reference exception?
To prevent an X/Y problem, the goal is to simply record what object causes a null reference exception to be thrown, since the...
Read more >MemberExpression Class (System.Linq.Expressions)
Gets the containing object of the field or property. Member. Gets the field or property to be accessed. NodeType. Returns the node type...
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
@despairblue thank you! This is great! Shouldn’t be too hard to make work.
With #462 it looks like
which is better. But we should also be able to break the
.to.have.property()