2020-05-01 14:40:43 +02:00
|
|
|
/*
|
|
|
|
|
* Copyright (c) 2020, Emanuele Torre <torreemanuele6@gmail.com>
|
2021-04-22 22:51:19 +02:00
|
|
|
* Copyright (c) 2020-2021, Linus Groh <linusg@serenityos.org>
|
2020-05-01 14:40:43 +02:00
|
|
|
*
|
2021-04-22 01:24:48 -07:00
|
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
2020-05-01 14:40:43 +02:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include <LibJS/Console.h>
|
2020-09-29 21:15:06 +02:00
|
|
|
#include <LibJS/Runtime/GlobalObject.h>
|
2020-05-01 14:40:43 +02:00
|
|
|
|
|
|
|
|
namespace JS {
|
|
|
|
|
|
2020-09-29 21:15:06 +02:00
|
|
|
Console::Console(GlobalObject& global_object)
|
|
|
|
|
: m_global_object(global_object)
|
2020-05-01 14:40:43 +02:00
|
|
|
{
|
|
|
|
|
}
|
|
|
|
|
|
2021-02-21 21:11:49 +01:00
|
|
|
VM& Console::vm()
|
|
|
|
|
{
|
|
|
|
|
return m_global_object.vm();
|
|
|
|
|
}
|
|
|
|
|
|
2020-05-04 13:20:25 +02:00
|
|
|
Value Console::debug()
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
{
|
2021-03-02 00:12:06 +01:00
|
|
|
#ifdef __serenity__
|
2021-02-21 21:11:49 +01:00
|
|
|
dbgln("\033[32;1m(js debug)\033[0m {}", vm().join_arguments());
|
2021-03-02 00:12:06 +01:00
|
|
|
#endif
|
2020-05-04 15:57:05 +02:00
|
|
|
if (m_client)
|
|
|
|
|
return m_client->debug();
|
2020-05-04 13:20:25 +02:00
|
|
|
return js_undefined();
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
}
|
|
|
|
|
|
2020-05-04 13:20:25 +02:00
|
|
|
Value Console::error()
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
{
|
2021-03-02 00:12:06 +01:00
|
|
|
#ifdef __serenity__
|
2021-02-21 21:11:49 +01:00
|
|
|
dbgln("\033[32;1m(js error)\033[0m {}", vm().join_arguments());
|
2021-03-02 00:12:06 +01:00
|
|
|
#endif
|
2020-05-04 15:57:05 +02:00
|
|
|
if (m_client)
|
|
|
|
|
return m_client->error();
|
2020-05-04 13:20:25 +02:00
|
|
|
return js_undefined();
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
}
|
|
|
|
|
|
2020-05-04 13:20:25 +02:00
|
|
|
Value Console::info()
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
{
|
2021-03-02 00:12:06 +01:00
|
|
|
#ifdef __serenity__
|
2021-02-21 21:11:49 +01:00
|
|
|
dbgln("\033[32;1m(js info)\033[0m {}", vm().join_arguments());
|
2021-03-02 00:12:06 +01:00
|
|
|
#endif
|
2020-05-04 15:57:05 +02:00
|
|
|
if (m_client)
|
|
|
|
|
return m_client->info();
|
2020-05-04 13:20:25 +02:00
|
|
|
return js_undefined();
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
}
|
|
|
|
|
|
2020-05-04 13:20:25 +02:00
|
|
|
Value Console::log()
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
{
|
2021-03-02 00:12:06 +01:00
|
|
|
#ifdef __serenity__
|
2021-02-21 21:11:49 +01:00
|
|
|
dbgln("\033[32;1m(js log)\033[0m {}", vm().join_arguments());
|
2021-03-02 00:12:06 +01:00
|
|
|
#endif
|
2020-05-04 15:57:05 +02:00
|
|
|
if (m_client)
|
|
|
|
|
return m_client->log();
|
2020-05-04 13:20:25 +02:00
|
|
|
return js_undefined();
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
}
|
|
|
|
|
|
2020-05-04 13:20:25 +02:00
|
|
|
Value Console::warn()
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
{
|
2021-03-02 00:12:06 +01:00
|
|
|
#ifdef __serenity__
|
2021-02-21 21:11:49 +01:00
|
|
|
dbgln("\033[32;1m(js warn)\033[0m {}", vm().join_arguments());
|
2021-03-02 00:12:06 +01:00
|
|
|
#endif
|
2020-05-04 15:57:05 +02:00
|
|
|
if (m_client)
|
|
|
|
|
return m_client->warn();
|
2020-05-04 13:20:25 +02:00
|
|
|
return js_undefined();
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
}
|
|
|
|
|
|
2020-05-04 13:20:25 +02:00
|
|
|
Value Console::clear()
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
{
|
2020-05-04 15:57:05 +02:00
|
|
|
if (m_client)
|
|
|
|
|
return m_client->clear();
|
2020-05-04 13:20:25 +02:00
|
|
|
return js_undefined();
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
}
|
|
|
|
|
|
2020-05-04 13:20:25 +02:00
|
|
|
Value Console::trace()
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
{
|
2020-05-04 15:57:05 +02:00
|
|
|
if (m_client)
|
|
|
|
|
return m_client->trace();
|
2020-05-04 13:20:25 +02:00
|
|
|
return js_undefined();
|
LibJS: Add ConsoleMessage concept
A ConsoleMessage is a struct cointaining:
* AK::String text; represents the text of the message sent
to the console.
* ConsoleMessageKind kind; represents the kind of JS `console` function
from which the message was sent.
Now, Javascript `console` functions only send a ConsoleMessage to the
Interpreter's Console instead of printing text directly to stdout.
The Console then stores the recived ConsoleMessage in
Console::m_messages; the Console does not print to stdout by default.
You can set Console::on_new_message to a void(ConsoleMessage&); this
function will get call everytime a new message is added to the Console's
messages and can be used, for example, to print ConsoleMessages to
stdout or to color the output based on the kind of ConsoleMessage.
In this patch, I also:
* Re-implement all the previously implemented functions in the
JavaScript ConsoleObject, as wrappers around Console functions
that add new message to the Console.
* Implement console.clear() like so:
- m_messages get cleared;
- a new_message with kind set ConsoleMessageKind::Clear gets added
to m_messages, its text is an empty AK::String;
* Give credit to linusg in Console.cpp since I used his
console.trace() algorithm in Console::trace().
I think that having this abstration will help us in the implementation
of a browser console or a JS debugger. We could also add more MetaData
to ConsoleMessage, e.g. Object IDs of the arguments passed to console
functions in order to make hyperlinks, Timestamps, ecc.; which could be
interesting to see.
This will also help in implementing a `/bin/js` option to make, for
example, return a ConsoleMessageWrapper to console functions instead of
undefined. This will be useful to make tests for functions like
console.count() and console.countClear(). :^)
2020-05-01 17:34:43 +02:00
|
|
|
}
|
|
|
|
|
|
2020-05-04 13:20:25 +02:00
|
|
|
Value Console::count()
|
2020-05-01 15:19:43 +02:00
|
|
|
{
|
2020-05-04 15:57:05 +02:00
|
|
|
if (m_client)
|
|
|
|
|
return m_client->count();
|
2020-05-04 13:20:25 +02:00
|
|
|
return js_undefined();
|
2020-05-01 15:19:43 +02:00
|
|
|
}
|
|
|
|
|
|
2020-05-04 13:20:25 +02:00
|
|
|
Value Console::count_reset()
|
2020-05-01 15:19:43 +02:00
|
|
|
{
|
2020-05-04 15:57:05 +02:00
|
|
|
if (m_client)
|
|
|
|
|
return m_client->count_reset();
|
2020-05-04 14:18:15 +02:00
|
|
|
return js_undefined();
|
|
|
|
|
}
|
|
|
|
|
|
2021-04-18 17:08:14 +02:00
|
|
|
Value Console::assert_()
|
|
|
|
|
{
|
|
|
|
|
if (m_client)
|
|
|
|
|
return m_client->assert_();
|
|
|
|
|
return js_undefined();
|
|
|
|
|
}
|
|
|
|
|
|
2020-05-04 14:18:15 +02:00
|
|
|
unsigned Console::counter_increment(String label)
|
|
|
|
|
{
|
|
|
|
|
auto value = m_counters.get(label);
|
|
|
|
|
if (!value.has_value()) {
|
|
|
|
|
m_counters.set(label, 1);
|
|
|
|
|
return 1;
|
2020-05-04 12:02:16 +02:00
|
|
|
}
|
2020-05-01 15:19:43 +02:00
|
|
|
|
2020-05-04 14:18:15 +02:00
|
|
|
auto new_value = value.value() + 1;
|
|
|
|
|
m_counters.set(label, new_value);
|
|
|
|
|
return new_value;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
bool Console::counter_reset(String label)
|
|
|
|
|
{
|
|
|
|
|
if (!m_counters.contains(label))
|
|
|
|
|
return false;
|
|
|
|
|
|
2020-05-01 15:19:43 +02:00
|
|
|
m_counters.remove(label);
|
2020-05-04 14:18:15 +02:00
|
|
|
return true;
|
2020-05-01 15:19:43 +02:00
|
|
|
}
|
|
|
|
|
|
2020-09-29 21:15:06 +02:00
|
|
|
VM& ConsoleClient::vm()
|
|
|
|
|
{
|
|
|
|
|
return global_object().vm();
|
|
|
|
|
}
|
|
|
|
|
|
2020-06-02 13:54:26 +01:00
|
|
|
Vector<String> ConsoleClient::get_trace() const
|
|
|
|
|
{
|
|
|
|
|
Vector<String> trace;
|
2020-09-29 21:15:06 +02:00
|
|
|
auto& call_stack = m_console.global_object().vm().call_stack();
|
2020-06-02 13:54:26 +01:00
|
|
|
// -2 to skip the console.trace() call frame
|
|
|
|
|
for (ssize_t i = call_stack.size() - 2; i >= 0; --i)
|
2020-11-07 11:07:17 +01:00
|
|
|
trace.append(call_stack[i]->function_name);
|
2020-06-02 13:54:26 +01:00
|
|
|
return trace;
|
|
|
|
|
}
|
|
|
|
|
|
2020-05-01 14:40:43 +02:00
|
|
|
}
|