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.
Default Emit Behavior for v2
See original GitHub issueAnother issue to be aware of that should be resolved for v2:
Currently default values for enumerations (the first value) are emitted.
So in the example of TestClassPrimitiveTypes, it currently expects this in the results:
<PropEnum>EnumValue1</PropEnum>
When in fact that should not be emitted at all.
Issue Analytics
- State:
- Created 7 years ago
- Comments:17 (17 by maintainers)
Top Results From Across the Web
emits Option | Vue 3 Migration Guide
Vue 3 now offers an emits option, similar to the existing props option. This option can be used to define the events that...
Read more >$emit and $on strange behavior - Vue2
This is not answering my question. There's obviously 2 ways to emit the event from a child to a parent, why $on does...
Read more >Explore LiveData & StateFlow Value Emitting Behavior
In short, the value is emitted and cached though not displayed. Emitted values are not lost at all, but are just not being...
Read more >BehaviorSubject - RxJS Reference
BehaviorSubject is a variant of a Subject which has a notion of the current value that it stores and emits to all new...
Read more >Is it possible to emit event from component inside slot #4332
You cannot listen to events on <slot> . It can end up rendering anything: text, plain element, multiple nodes... the behavior will be...
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
OK. It is good idea!
Haha thanks. We still haven’t decided on the default behavior, however. 😃 Should it be
cfg.Emit(EmitBehaviors.WhenNotNull)? I think this is the most expected behavior while also being performant.