ladybird/Userland/Libraries/LibJS/Runtime/Intl/Intl.h

/*
 * Copyright (c) 2021, Linus Groh <linusg@serenityos.org>
 *
 * SPDX-License-Identifier: BSD-2-Clause
 */

#pragma once

#include <LibJS/Runtime/Object.h>

namespace JS::Intl {

class Intl final : public Object {
    JS_OBJECT(Intl, Object);

public:
    explicit Intl(Realm&);
    virtual void initialize(Realm&) override;
    virtual ~Intl() override = default;

private:
    JS_DECLARE_NATIVE_FUNCTION(get_canonical_locales);
    JS_DECLARE_NATIVE_FUNCTION(supported_values_of);
};

}
LibJS: Add the Intl namespace object :^) This is the start of implementing ECMA-402 in LibJS, better known as the ECMAScript Internationalization API. Much like Temporal this gets its own subdirectory (Runtime/Intl/) as well as a new C++ namespace (JS::Intl) so we don't have to prefix all the files and classes with "Intl". https://tc39.es/ecma402/ 2021-08-08 18:27:28 +01:00			`/*`
			`* Copyright (c) 2021, Linus Groh <linusg@serenityos.org>`
			`*`
			`* SPDX-License-Identifier: BSD-2-Clause`
			`*/`

			`#pragma once`

			`#include <LibJS/Runtime/Object.h>`

			`namespace JS::Intl {`

			`class Intl final : public Object {`
			`JS_OBJECT(Intl, Object);`

			`public:`
LibJS+LibWeb: Replace GlobalObject with Realm in object constructors No functional changes - we can still very easily get to the global object via `Realm::global_object()`. This is in preparation of moving the intrinsics to the realm and no longer having to pass a global object when allocating any object. In a few (now, and many more in subsequent commits) places we get a realm using `GlobalObject::associated_realm()`, this is intended to be temporary. For example, create() functions will later receive the same treatment and are passed a realm instead of a global object. 2022-08-16 00:20:49 +01:00			`explicit Intl(Realm&);`
LibJS+LibWeb: Replace GlobalObject with Realm in initialize() functions This is a continuation of the previous commit. Calling initialize() is the first thing that's done after allocating a cell on the JS heap - and in the common case of allocating an object, that's where properties are assigned and intrinsics occasionally accessed. Since those are supposed to live on the realm eventually, this is another step into that direction. 2022-08-16 00:20:49 +01:00			`virtual void initialize(Realm&) override;`
LibJS: Add the Intl namespace object :^) This is the start of implementing ECMA-402 in LibJS, better known as the ECMAScript Internationalization API. Much like Temporal this gets its own subdirectory (Runtime/Intl/) as well as a new C++ namespace (JS::Intl) so we don't have to prefix all the files and classes with "Intl". https://tc39.es/ecma402/ 2021-08-08 18:27:28 +01:00			`virtual ~Intl() override = default;`
LibJS: Implement Intl.getCanonicalLocales 2021-08-25 09:41:25 -04:00
			`private:`
LibJS: Convert Intl.getCanonicalLocales() function to ThrowCompletionOr 2021-10-22 22:45:54 +01:00			`JS_DECLARE_NATIVE_FUNCTION(get_canonical_locales);`
LibJS: Implement Intl.supportedValuesOf This is a stage 3 ECMA-402 proposal: https://tc39.es/proposal-intl-enumeration/ 2022-01-30 17:36:23 -05:00			`JS_DECLARE_NATIVE_FUNCTION(supported_values_of);`
LibJS: Add the Intl namespace object :^) This is the start of implementing ECMA-402 in LibJS, better known as the ECMAScript Internationalization API. Much like Temporal this gets its own subdirectory (Runtime/Intl/) as well as a new C++ namespace (JS::Intl) so we don't have to prefix all the files and classes with "Intl". https://tc39.es/ecma402/ 2021-08-08 18:27:28 +01:00			`};`

			`}`