-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Blazor/WASM] Unable to enumerate over IEnumerable in the Watch Window #49442
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @thaystg Issue DetailsDescribe the bugYou cannot view the results of an IEnumerable in the watch window. To Reproduce
Expected ResultsAn option will appear in the watch window called "Results View" that will execute the enumerable and display the results Actual ResultsNo option exists to view the contents of the WASM Output.NET Core Output
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDescribe the bugYou cannot view the results of an IEnumerable in the watch window. To Reproduce
Expected ResultsAn option will appear in the watch window called "Results View" that will execute the enumerable and display the results Actual ResultsNo option exists to view the contents of the WASM Output.NET Core Output
|
We don't support DebuggerTypeProxy and DebuggerDisplay yet. |
Describe the bug
You cannot view the results of an IEnumerable in the watch window.
To Reproduce
Bar
using the code belowFetchData.razor
using the code below.foo
variable is initializedfoo
to the watch windowfoo
variable in the watch windowSequence
property (It'sIEnumerable<int>
)Expected Results
An option will appear in the watch window called "Results View" that will execute the enumerable and display the results
Actual Results
No option exists to view the contents of the
IEnumerable
property.WASM Output
.NET Core Output
The text was updated successfully, but these errors were encountered: