Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-10-31 13:20:59 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Libraries/LibURL/Pattern/Pattern.h

98 lines
3.1 KiB
C
Raw Normal View History

LibURL: Add representations of URLPattern{Init,Options,Input} The URLPattern spec is intended to be implemented inside of LibURL, with LibWeb only responsible for the IDL conversion layer, in a similar manner to how URL is implemented.
2025-01-11 22:54:57 +13:00
/*
* Copyright (c) 2025, Shannon Booth <shannon@serenityos.org>
*
* SPDX-License-Identifier: BSD-2-Clause
*/
#pragma once
LibURL: Add a representation of a URL Pattern 'result' This is the return value of a URLPattern after `exec` is called on it. It conveys information about the named (or unammed) regex groups matched for each component of the URL. For example, ``` let p = new URLPattern({ hostname: "{:subdomain.}*example.com" }); const result = pattern.exec({ hostname: "foo.bar.example.com" }); console.log(result.hostname.groups.subdomain); ``` Will log 'foo.bar'.
2025-01-13 22:24:18 +13:00
#include <AK/HashMap.h>
#include <AK/String.h>
LibURL: Add representations of URLPattern{Init,Options,Input} The URLPattern spec is intended to be implemented inside of LibURL, with LibWeb only responsible for the IDL conversion layer, in a similar manner to how URL is implemented.
2025-01-11 22:54:57 +13:00
#include <AK/Variant.h>
LibURL: Add a representation of a URL Pattern 'result' This is the return value of a URLPattern after `exec` is called on it. It conveys information about the named (or unammed) regex groups matched for each component of the URL. For example, ``` let p = new URLPattern({ hostname: "{:subdomain.}*example.com" }); const result = pattern.exec({ hostname: "foo.bar.example.com" }); console.log(result.hostname.groups.subdomain); ``` Will log 'foo.bar'.
2025-01-13 22:24:18 +13:00
#include <AK/Vector.h>
LibURL/Pattern: Add a representation of a URL Pattern This is the core object behind a URL pattern which when constructed can be used for matching the pattern against URLs. However, the implementation here is missing key functions such as the constructor and the 'test'/'exec' functions as that relies on a significant amount of supporting URLPattern infrastructure such as two different parsers and a tokenizer. However, this is enough for us to implement some more of the IDL wrapper layer of this specification.
2025-02-04 15:10:14 +13:00
#include <LibURL/Pattern/Component.h>
LibURL: Add representations of URLPattern{Init,Options,Input} The URLPattern spec is intended to be implemented inside of LibURL, with LibWeb only responsible for the IDL conversion layer, in a similar manner to how URL is implemented.
2025-01-11 22:54:57 +13:00
#include <LibURL/Pattern/Init.h>
LibURL/Pattern: Add some scaffolding for the URLPattern constructor
2025-03-01 14:43:15 +13:00
#include <LibURL/Pattern/PatternError.h>
LibURL: Add representations of URLPattern{Init,Options,Input} The URLPattern spec is intended to be implemented inside of LibURL, with LibWeb only responsible for the IDL conversion layer, in a similar manner to how URL is implemented.
2025-01-11 22:54:57 +13:00
namespace URL::Pattern {
// https://urlpattern.spec.whatwg.org/#typedefdef-urlpatterninput
using Input = Variant<String, Init>;
// https://urlpattern.spec.whatwg.org/#dictdef-urlpatternoptions
struct Options {
bool ignore_case { false };
};
LibURL: Add a representation of a URL Pattern 'result' This is the return value of a URLPattern after `exec` is called on it. It conveys information about the named (or unammed) regex groups matched for each component of the URL. For example, ``` let p = new URLPattern({ hostname: "{:subdomain.}*example.com" }); const result = pattern.exec({ hostname: "foo.bar.example.com" }); console.log(result.hostname.groups.subdomain); ``` Will log 'foo.bar'.
2025-01-13 22:24:18 +13:00
// https://urlpattern.spec.whatwg.org/#dictdef-urlpatterncomponentresult
struct ComponentResult {
String input;
OrderedHashMap<String, Variant<String, Empty>> groups;
};
// https://urlpattern.spec.whatwg.org/#dictdef-urlpatternresult
struct Result {
Vector<Input> inputs;
ComponentResult protocol;
ComponentResult username;
ComponentResult password;
ComponentResult hostname;
ComponentResult port;
ComponentResult pathname;
ComponentResult search;
ComponentResult hash;
};
LibURL/Pattern: Add a representation of a URL Pattern This is the core object behind a URL pattern which when constructed can be used for matching the pattern against URLs. However, the implementation here is missing key functions such as the constructor and the 'test'/'exec' functions as that relies on a significant amount of supporting URLPattern infrastructure such as two different parsers and a tokenizer. However, this is enough for us to implement some more of the IDL wrapper layer of this specification.
2025-02-04 15:10:14 +13:00
// https://urlpattern.spec.whatwg.org/#url-pattern
class Pattern {
public:
LibURL/Pattern: Add some scaffolding for the URLPattern constructor
2025-03-01 14:43:15 +13:00
static PatternErrorOr<Pattern> create(Input const&, Optional<String> const& base_url = {}, Options const& = {});
LibURL/Pattern: Add a representation of a URL Pattern This is the core object behind a URL pattern which when constructed can be used for matching the pattern against URLs. However, the implementation here is missing key functions such as the constructor and the 'test'/'exec' functions as that relies on a significant amount of supporting URLPattern infrastructure such as two different parsers and a tokenizer. However, this is enough for us to implement some more of the IDL wrapper layer of this specification.
2025-02-04 15:10:14 +13:00
bool has_regexp_groups() const;
Component const& protocol_component() const { return m_protocol_component; }
Component const& username_component() const { return m_username_component; }
Component const& password_component() const { return m_password_component; }
Component const& hostname_component() const { return m_hostname_component; }
Component const& port_component() const { return m_port_component; }
Component const& pathname_component() const { return m_pathname_component; }
Component const& search_component() const { return m_search_component; }
Component const& hash_component() const { return m_hash_component; }
private:
// https://urlpattern.spec.whatwg.org/#url-pattern-protocol-component
// protocol component, a component
Component m_protocol_component;
// https://urlpattern.spec.whatwg.org/#url-pattern-username-component
// username component, a component
Component m_username_component;
// https://urlpattern.spec.whatwg.org/#url-pattern-password-component
// password component, a component
Component m_password_component;
// https://urlpattern.spec.whatwg.org/#url-pattern-hostname-component
// hostname component, a component
Component m_hostname_component;
// https://urlpattern.spec.whatwg.org/#url-pattern-port-component
// port component, a component
Component m_port_component;
// https://urlpattern.spec.whatwg.org/#url-pattern-pathname-component
// pathname component, a component
Component m_pathname_component;
// https://urlpattern.spec.whatwg.org/#url-pattern-search-component
// search component, a component
Component m_search_component;
// https://urlpattern.spec.whatwg.org/#url-pattern-hash-component
// hash component, a component
Component m_hash_component;
};
LibURL: Add representations of URLPattern{Init,Options,Input} The URLPattern spec is intended to be implemented inside of LibURL, with LibWeb only responsible for the IDL conversion layer, in a similar manner to how URL is implemented.
2025-01-11 22:54:57 +13:00
}
Reference in a new issue Copy permalink