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
Debug directives require adding comments directly to the source code.
This attribute can be used to set hidden breakpoints without modifying the source code.
Its value is an array of objects with the following child attributes.
target: string : File path or function name
File Mode : If / or \ is included, it is treated as a file path; a glob may also be specified
Callable Symbol Mode: Names of functions, methods, and dynamic properties. It is possible to use wildcards
line: number : Line number to be placed. If a negative value is specified, it is the offset from the end. Also, an object with the following fields can be specified to set breakpoints on lines that match the condition
pattern : Regular expression to be applied to each line
ignoreCase: boolean
select: 'first' | 'last' | 'all' | number | number[] : Controls whether some or all breakpoints are set when multiple lines are matched
offset: number
condition: string : Condition for enabling breakpoint
hitCondition: string : Hit condition for enabling breakpoint
log: string : A log message to be output at break
break: boolean : If false is specified, no break is made. If omitted, false is set if log or action is specified, otherwise true
action: string : The following string can be specified to define the action to be executed at break
You can also specify an object with the following fields In this case, you can use the UI for exception breakpoints to change the enable/disable of the specified breakpoints.
label: string : Labels displayed on the UI for exception breakpoints
default: boolean : Default setting for debugging. Enabled (true), Disabled (false). Default is true
breakpoints : An array consisting of objects with the fields described above
Debug directives require adding comments directly to the source code.
This attribute can be used to set hidden breakpoints without modifying the source code.
Its value is an array of objects with the following child attributes.
target: string
: File path or function nameFile Mode
: If/
or\
is included, it is treated as a file path; a glob may also be specifiedCallable Symbol Mode
: Names of functions, methods, and dynamic properties. It is possible to use wildcardsline: number
: Line number to be placed. If a negative value is specified, it is the offset from the end. Also, an object with the following fields can be specified to set breakpoints on lines that match the conditionpattern
: Regular expression to be applied to each lineignoreCase: boolean
select: 'first' | 'last' | 'all' | number | number[]
: Controls whether some or all breakpoints are set when multiple lines are matchedoffset: number
condition: string
: Condition for enabling breakpointhitCondition: string
: Hit condition for enabling breakpointlog: string
: A log message to be output at breakbreak: boolean
: Iffalse
is specified, no break is made. If omitted,false
is set iflog
oraction
is specified, otherwisetrue
action: string
: The following string can be specified to define the action to be executed at breakYou can also specify an object with the following fields In this case, you can use the UI for exception breakpoints to change the enable/disable of the specified breakpoints.
label: string
: Labels displayed on the UI for exception breakpointsdefault: boolean
: Default setting for debugging. Enabled (true
), Disabled (false
). Default istrue
breakpoints
: An array consisting of objects with the fields described aboveGrouped strings with
pattern
can be output in the log.The text was updated successfully, but these errors were encountered: