You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
httpclient.execute takes a new FutureCallback as a calling argument. FutureCallback is fully defined inline and has the functions completed, failed and cancelled defined within it. These three functions are nested in FutureCallback and the Outline Viewer should display them as indented under it. They are not.
Expected that the functions should be indented and placed in expand/collapse sublists under FutureCallback in the Outline Viewer.
VS Code version: Code 1.25.0 (0f080e5, 2018-07-05T13:02:28.333Z)
OS version: Darwin x64 17.6.0
System Info
Item
Value
CPUs
Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz (2 x 2400)
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.
Issue Type: Bug
Using Pablo Moretti's Async Java example as a test case AsyncClientHttpExchangeFutureCallback.java.
httpclient.execute
takes anew FutureCallback
as a calling argument.FutureCallback
is fully defined inline and has the functionscompleted
,failed
andcancelled
defined within it. These three functions are nested inFutureCallback
and the Outline Viewer should display them as indented under it. They are not.Expected that the functions should be indented and placed in expand/collapse sublists under
FutureCallback
in the Outline Viewer.VS Code version: Code 1.25.0 (0f080e5, 2018-07-05T13:02:28.333Z)
OS version: Darwin x64 17.6.0
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: disabled_off
native_gpu_memory_buffers: enabled
rasterization: unavailable_software
video_decode: enabled
video_encode: enabled
vpx_decode: enabled
webgl: enabled
webgl2: enabled
Extensions (58)
The text was updated successfully, but these errors were encountered: