appium 2.0.0-beta.9 → 2.0.0-rc.2

package/LICENSE

@@ -186,7 +186,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright JS Foundation and other contributors, https://js.foundation
+   Copyright OpenJS Foundation and other contributors, https://openjsf.org/
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

package/README.md

@@ -1,51 +1,161 @@
 ## Appium
 
 [![NPM version](https://badge.fury.io/js/appium.svg)](https://npmjs.org/package/appium)
-[![Dependency Status](https://david-dm.org/appium/appium.svg)](https://david-dm.org/appium/appium)
-[![devDependency Status](https://david-dm.org/appium/appium/dev-status.svg)](https://david-dm.org/appium/appium#info=devDependencies)
-
 [![Monthly Downloads](https://img.shields.io/npm/dm/appium.svg)](https://npmjs.org/package/appium)
 
 [![FOSSA Status](https://app.fossa.io/api/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Fappium%2Fappium.svg?type=shield)](https://app.fossa.io/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Fappium%2Fappium?ref=badge_shield)
 
+[![StandWithUkraine](https://raw.githubusercontent.com/vshymanskyy/StandWithUkraine/main/badges/StandWithUkraine.svg)](https://github.com/vshymanskyy/StandWithUkraine/)
+
+[![Stand With Ukraine](https://raw.githubusercontent.com/vshymanskyy/StandWithUkraine/main/banner2-direct.svg)](https://vshymanskyy.github.io/StandWithUkraine/)
+
 Appium is an open-source, cross-platform test automation tool for native,
-hybrid, and mobile web and desktop apps. We support simulators (iOS), emulators
-(Android), and real devices (iOS, Android, Windows, Mac).
+hybrid, mobile web and desktop apps. Initially created to automate iOS and Android mobile
+applications Appium has grown to a full-featured platform that provides [WebDriver](https://www.w3.org/TR/webdriver/)-based automation possibilities for the whole set of different mobile and desktop platforms.
+See the full list of
+[officially-supported](https://appium.io/docs/en/latest/ecosystem/#drivers) and
+[third-party](https://appium.io/docs/en/latest/ecosystem/#other-drivers) drivers for more details.
+
+:bangbang: Major documentation revision in progress
+
+:bangbang: Appium core team does not maintain Appium 1.x anymore since the 1st of January 2022. All recent versions of officially supported platform drivers are not compatible to Appium 1.x anymore, and require Appium 2 to run. [Please read the migration guide from 1.x to 2.0](https://appium.io/docs/en/latest/guides/migrating-1-to-2/) to manage the Appium server.
+
+Appium is in the final stages of a major revision (to version 2.0). As such, the documentation
+found around the web may not be correct. The current Appium 2.0 documentation is very much in
+progress. Currently, it can be found [here](https://appium.io/docs/en/latest/).
+
+### Requirements
+
+- macOS, Linux or Windows operating system
+- Node.js 14+
+- NPM (Node Package Manager) 8+
+
+These are only server requirements. Each driver might have its own requirements. Consider checking the corresponding driver tutorial for more details.
 
-Want to skip straight to the action? Check out our [getting
-started](/docs/en/about-appium/getting-started.md) doc.
+### Server
 
-### Supported Platforms
+To install Appium 2 server using Node Package Manager (npm) run the following command:
+
+```bash
+npm install -g appium@next
+```
+
+:bangbang: Running `npm install -g appium` would still install Appium 1 because version 2 is in its late beta stage.
+
+### Drivers
 
 Appium supports app automation across a variety of platforms, like iOS,
 Android, and Windows. Each platform is supported by one or more "drivers",
-which know how to automate that particular platform. Choose a driver below for
-specific information about how that driver works and how to set it up:
-
-* iOS
-    * The [XCUITest Driver](/docs/en/drivers/ios-xcuitest.md)
-    * (DEPRECATED) The [UIAutomation Driver](/docs/en/drivers/ios-uiautomation.md)
-* Android
-    * The [Espresso Driver](/docs/en/drivers/android-espresso.md)
-    * The [UiAutomator2 Driver](/docs/en/drivers/android-uiautomator2.md)
-    * (DEPRECATED) The [UiAutomator Driver](/docs/en/drivers/android-uiautomator.md)
-* The [Windows Driver](/docs/en/drivers/windows.md) (for Windows Desktop apps)
-* The [Mac Driver](/docs/en/drivers/mac.md) (for Mac Desktop apps)
+which know how to automate that particular platform. Since version 2.0
+all drivers have been isolated from the Appium server app and can
+be managed independently using the [appium driver](https://appiumpro.com/editions/122-installing-appium-20-and-the-driver-and-plugins-cli) command line interface.
+
+In general, the drivers management in Appium 2 is as simple as:
+
+```bash
+# To install a new driver from npm
+appium driver install --source=npm appium-xcuitest-driver[@<version>]
+# To install a driver from a local folder (useful for developers)
+appium driver install --source=local /Users/me/sources/appium-xcuitest-driver
+# To install a new driver from github (hm, maybe it's time to publish it to NPM?)
+appium driver install --source=github --package=appium-xcuitest-driver appium/appium-xcuitest-driver
+
+# To list already installed drivers
+appium driver list --installed
+
+# To update a driver (it must be already installed)
+appium driver update xcuitest
+
+# To uninstall a driver (it won't last forever, wouldn't it?)
+appium driver uninstall xcuitest
+```
+
+You can find a full list of
+[officially-supported](https://appium.io/docs/en/latest/ecosystem/#drivers) and
+[third-party](https://appium.io/docs/en/latest/ecosystem/#other-drivers) drivers at
+the current Appium 2.0 documentation.
+
+### Plugins
+
+The concept of plugins is something new that has been added exclusively to Appium2. Plugins allow you to extend server functionality without changing the server code. Plugins could be managed similarly to drivers:
+
+```bash
+# To install an officially supported plugin
+appium plugin install images
+# To install a plugin from a local folder (useful for developers)
+appium plugin install --source=local /Users/me/sources/images
+# To install a new plugin from npm
+appium plugin install --source=npm appium-device-farm
+
+# To list already installed plugins
+appium plugin list --installed
+
+# To update a plugins (it must be already installed)
+appium plugin update appium-device-farm
+
+# To uninstall a plugin
+appium plugin uninstall appium-device-farm
+```
+
+The main difference between drivers and plugins is that the latter must be explicitly enabled on server startup after it was installed (drivers are enabled by default after installation):
+
+```bash
+appium server --use-plugins=device-farm,images
+```
+
+You can find a full list of
+[officially-supported](https://appium.io/docs/en/latest/ecosystem/#plugins) and
+[third-party](https://appium.io/docs/en/latest/ecosystem/#other-plugins) plugins at
+the current Appium 2.0 documentation.
+
+
+### Server Command Line Interface
+
+In order to start sending commands to Appium over the wire it must be listening
+on the URL where your client library expects it to listen.
+Use the following commands to run and configure Appium server:
+
+```bash
+# Start the server on the default port and host (e.g. http://0.0.0.0:4723/)
+appium server
+# Start the server on the given port, host and use the base path prefix (the default prefix is /)
+appium server -p 9000 -a 127.0.0.1 -pa /wd/hub
+
+# Get the list of all supported command line parameters.
+# This list would also include descriptions of driver-specific
+# command line arguments for all installed drivers.
+# Each driver and plugin must have their command line arguments
+# exposed in a special JSON schema declared as a part of the corresponding
+# package.json file.
+appium server --help
+```
+
+Appium supports execution of parallel server processes as well as parallel driver sessions within
+single server process. Refer the corresponding driver documentations regarding which mode is optimal
+for the particular driver or whether it supports parallel sessions.
 
 ### Why Appium?
 
-1. You don't have to recompile your app or modify it in any way, due
+1. You usually don't have to recompile your app or modify it in any way, due
    to the use of standard automation APIs on all platforms.
 2. You can write tests with your favorite dev tools using any
    [WebDriver](https://w3c.github.io/webdriver/webdriver-spec.html)-compatible
-   language such as Java, Objective-C, JavaScript (Node), PHP, Python, Ruby,
-   C#, Clojure, or Perl with the Selenium WebDriver API and [language-specific
-   client libraries](/docs/en/about-appium/appium-clients.md).
+   language such as [Java](https://github.com/appium/java-client),
+   [JavaScript](https://webdriver.io/), [Python](https://github.com/appium/python-client),
+   [Ruby](https://github.com/appium/ruby_lib), [C#](https://github.com/appium/dotnet-client)
+   with the Selenium WebDriver API. There are also various third party
+   client implementations for other languages.
 3. You can use any testing framework.
-4. Appium has built-in mobile web and hybrid app support. Within the same
-   script, you can switch seamlessly between native app automation and webview
-   automation, all using the WebDriver model that's already the standard for
-   web automation.
+4. Some drivers, like xcuitest and uiautomator2 ones have built-in mobile web and
+   hybrid app support. Within the same script, you can switch seamlessly between native
+   app automation and webview automation, all using the WebDriver model that's already
+   the standard for web automation.
+5. You can run your automated tests locally and in a cloud. There are multiple
+   cloud providers that support various Appium drivers (mostly
+   targeting iOS and Android mobile automation).
+6. [Appium Inspector](https://github.com/appium/appium-inspector) allows
+   visual debugging of automated tests and could be extremely useful for
+   beginners.
 
 Investing in the
 [WebDriver](https://w3c.github.io/webdriver/webdriver-spec.html) protocol means
@@ -59,35 +169,21 @@ Java/Kotlin. Appium opens up the possibility of true cross-platform native app
 automation, for mobile and beyond. Finally!
 
 If you're new to Appium or want a more comprehensive description of what this is all
-about, please read our [Introduction to Appium
-Concepts](/docs/en/about-appium/intro.md).
+about, please read our [Intro to Appium](https://appium.io/docs/en/latest/intro/).
 
-### Requirements
+### Quickstart
 
-Your environment needs to be set up for the particular platforms that you want
-to run tests on. Each of the drivers above documents the requirements for their
-particular brand of automation. At a minimum, you will need to be able to run
-Node.js 10+.
-
-### Get Started
-
-Check out our [Getting Started](/docs/en/about-appium/getting-started.md) guide
+Check out our [Quickstart](https://appium.io/docs/en/latest/quickstart/) guide
 to get going with Appium.
 
 There is also a sample code that contains [many examples of tests in a variety
-of different languages](https://github.com/appium/appium/tree/master/sample-code)!
+of different languages](https://github.com/appium/appium/tree/1.x/sample-code)!
 
 ### Documentation
 
-For prettily-rendered docs, please visit [appium.io](http://appium.io). You can
-always find the full list of Appium doc pages at [Appium's GitHub
-Repo](https://github.com/appium/appium/tree/master/docs/en/) as well.
-
-[update-appium-io.yml](https://github.com/appium/appium/blob/master/ci-jobs/update-appium-io.yml) creates a PR
-by [CI job](https://dev.azure.com/AppiumCI/Appium%20CI/_build?definitionId=37).
-in the appium.io repository with the documentation update.
-
-Once the PR has been merged, the latest documentation will be in [appium.io](http://appium.io)
+For prettily-rendered docs, please visit [Appium Documentation](https://appium.io).
+You can always find the full list of Appium doc pages at [Appium's GitHub
+Repo](https://github.com/appium/appium/tree/master/packages/appium/docs) as well.
 
 ### Contributing
 
@@ -100,21 +196,16 @@ Interested in where Appium is heading in the future? Check out the [Roadmap](ROA
 
 ### Project History, Credits & Inspiration
 
-* [History](http://appium.io/history)
-* [Credits](/docs/en/contributing-to-appium/credits.md)
+* [History](https://appium.io/docs/en/latest/intro/history/)
 
 ### User Forums
 
-Announcements and debates often take place on the [Discussion
-Group](https://discuss.appium.io), be sure to sign up!
+Announcements and debates often take place on the [Discussion Group](https://discuss.appium.io),
+be sure to sign up!
 
 ### Troubleshooting
 
-We put together a [troubleshooting
-guide](/docs/en/writing-running-appium/other/troubleshooting.md).  Please have a look
-here first if you run into any problems. It contains instructions for checking
-a lot of common errors and how to get in touch with the community if you're
-stumped.
+Please find the troubleshooting guide at the corresponding driver repository/documentation.
 
 ### License
 

package/build/lib/appium.d.ts

@@ -0,0 +1,229 @@
+/**
+ * Thrown when Appium tried to proxy a command using a driver's `proxyCommand` method but the
+ * method did not exist
+ */
+export class NoDriverProxyCommandError extends Error {
+    constructor();
+    /**
+     * @type {Readonly<string>}
+     */
+    code: Readonly<string>;
+}
+export type DriverData = import('@appium/types').DriverData;
+export type DriverOpts = import('@appium/types').ServerArgs;
+export type Constraints = import('@appium/types').Constraints;
+export type AppiumServer = import('@appium/types').AppiumServer;
+export type ExtensionType = import('@appium/types').ExtensionType;
+export type DriverConfig = import('./extension/driver-config').DriverConfig;
+export type PluginType = import('@appium/types').PluginType;
+export type DriverType = import('@appium/types').DriverType;
+export type StringRecord = import('@appium/types').StringRecord;
+export type ExternalDriver = import('@appium/types').ExternalDriver;
+export type PluginClass = import('@appium/types').PluginClass;
+export type Plugin = import('@appium/types').Plugin;
+export type DriverClass = import('@appium/types').DriverClass<import('@appium/types').Driver>;
+export type AppiumSessionHandler = import('@appium/types').ISessionHandler<AppiumDriverConstraints, SessionHandlerCreateResult, SessionHandlerDeleteResult>;
+export type SessionHandlerCreateResult = SessionHandlerResult<[
+    innerSessionId: string,
+    caps: import('@appium/types').DriverCaps<Constraints>,
+    protocol: string | undefined
+]>;
+export type Core<C extends import("@appium/types").Constraints> = import('@appium/types').Core<C>;
+export type SessionHandlerDeleteResult = SessionHandlerResult<void>;
+/**
+ * Used by {@linkcode AppiumDriver.createSession } and {@linkcode AppiumDriver.deleteSession } to describe
+ * result.
+ */
+export type SessionHandlerResult<V> = {
+    value?: V | undefined;
+    error?: Error | undefined;
+    protocol?: string | undefined;
+};
+export type AppiumDriverConstraints = typeof desiredCapabilityConstraints;
+export type W3CAppiumDriverCaps = import('@appium/types').W3CDriverCaps<AppiumDriverConstraints>;
+/**
+ * @extends {DriverCore<AppiumDriverConstraints>}
+ */
+export class AppiumDriver extends DriverCore<{
+    readonly automationName: {
+        readonly presence: true;
+        readonly isString: true;
+    };
+    readonly platformName: {
+        readonly presence: true;
+        readonly isString: true;
+    };
+}, import("../../base-driver/build/lib/basedriver/core").StringRecord> {
+    /**
+     * @param {import('@appium/types').DriverOpts<AppiumDriverConstraints>} opts
+     */
+    constructor(opts: import('@appium/types').DriverOpts<AppiumDriverConstraints>);
+    /**
+     * Access to sessions list must be guarded with a Semaphore, because
+     * it might be changed by other async calls at any time
+     * It is not recommended to access this property directly from the outside
+     * @type {Record<string,ExternalDriver>}
+     */
+    sessions: Record<string, ExternalDriver>;
+    /**
+     * Access to pending drivers list must be guarded with a Semaphore, because
+     * it might be changed by other async calls at any time
+     * It is not recommended to access this property directly from the outside
+     * @type {Record<string,ExternalDriver[]>}
+     */
+    pendingDrivers: Record<string, ExternalDriver[]>;
+    /**
+     * List of active plugins
+     * @type {Map<PluginClass,string>}
+     */
+    pluginClasses: Map<PluginClass, string>;
+    /**
+     * map of sessions to actual plugin instances per session
+     * @type {Record<string,InstanceType<PluginClass>[]>}
+     */
+    sessionPlugins: Record<string, InstanceType<PluginClass>[]>;
+    /**
+     * some commands are sessionless, so we need a set of plugins for them
+     * @type {InstanceType<PluginClass>[]}
+     */
+    sessionlessPlugins: InstanceType<PluginClass>[];
+    /** @type {DriverConfig} */
+    driverConfig: DriverConfig;
+    /** @type {AppiumServer} */
+    server: AppiumServer;
+    /**
+     * @type {AppiumDriverConstraints}
+     * @readonly
+     */
+    readonly desiredCapConstraints: AppiumDriverConstraints;
+    /** @type {import('@appium/types').DriverOpts<AppiumDriverConstraints>} */
+    args: import('@appium/types').DriverOpts<AppiumDriverConstraints>;
+    sessionExists(sessionId: any): boolean;
+    driverForSession(sessionId: any): import("@appium/types").ExternalDriver<import("@appium/types").Constraints, string>;
+    getStatus(): Promise<{
+        build: import("../types").BuildInfo;
+    }>;
+    getSessions(): Promise<{
+        id: string;
+        capabilities: import("@appium/types").DriverCaps<import("@appium/types").Constraints>;
+    }[]>;
+    printNewSessionAnnouncement(driverName: any, driverVersion: any, driverBaseVersion: any): void;
+    /**
+     * Retrieves all CLI arguments for a specific plugin.
+     * @param {string} extName - Plugin name
+     * @returns {StringRecord} Arguments object. If none, an empty object.
+     */
+    getCliArgsForPlugin(extName: string): StringRecord;
+    /**
+     * Retrieves CLI args for a specific driver.
+     *
+     * _Any arg which is equal to its default value will not be present in the returned object._
+     *
+     * _Note that this behavior currently (May 18 2022) differs from how plugins are handled_ (see {@linkcode AppiumDriver.getCliArgsForPlugin}).
+     * @param {string} extName - Driver name
+     * @returns {StringRecord|undefined} Arguments object. If none, `undefined`
+     */
+    getCliArgsForDriver(extName: string): StringRecord | undefined;
+    /**
+     * Create a new session
+     * @param {W3CAppiumDriverCaps} jsonwpCaps JSONWP formatted desired capabilities
+     * @param {W3CAppiumDriverCaps} [reqCaps] Required capabilities (JSONWP standard)
+     * @param {W3CAppiumDriverCaps} [w3cCapabilities] W3C capabilities
+     * @returns {Promise<SessionHandlerCreateResult>}
+     */
+    createSession(jsonwpCaps: W3CAppiumDriverCaps, reqCaps?: W3CAppiumDriverCaps | undefined, w3cCapabilities?: W3CAppiumDriverCaps | undefined): Promise<SessionHandlerCreateResult>;
+    /**
+     *
+     * @param {ExternalDriver} driver
+     * @param {string} innerSessionId
+     */
+    attachUnexpectedShutdownHandler(driver: ExternalDriver, innerSessionId: string): void;
+    /**
+     *
+     * @param {((...args: any[]) => any)|(new(...args: any[]) => any)} InnerDriver
+     * @returns {Promise<DriverData[]>}}
+     * @privateRemarks The _intent_ is that `InnerDriver` is the class of a driver, but it only really
+     * needs to be a function or constructor.
+     */
+    curSessionDataForDriver(InnerDriver: ((...args: any[]) => any) | (new (...args: any[]) => any)): Promise<DriverData[]>;
+    /**
+     * @param {string} sessionId
+     */
+    deleteSession(sessionId: string): Promise<{
+        protocol: undefined;
+        value: void;
+        error?: undefined;
+    } | {
+        protocol: undefined;
+        error: any;
+        value?: undefined;
+    }>;
+    deleteAllSessions(opts?: {}): Promise<void>;
+    /**
+     * Get the appropriate plugins for a session (or sessionless plugins)
+     *
+     * @param {?string} sessionId - the sessionId (or null) to use to find plugins
+     * @returns {Array} - array of plugin instances
+     */
+    pluginsForSession(sessionId?: string | null): any[];
+    /**
+     * To get plugins for a command, we either get the plugin instances associated with the
+     * particular command's session, or in the case of sessionless plugins, pull from the set of
+     * plugin instances reserved for sessionless commands (and we lazily create plugin instances on
+     * first use)
+     *
+     * @param {string} cmd - the name of the command to find a plugin to handle
+     * @param {?string} sessionId - the particular session for which to find a plugin, or null if
+     * sessionless
+     */
+    pluginsToHandleCmd(cmd: string, sessionId?: string | null): any[];
+    /**
+     * Creates instances of all of the enabled Plugin classes
+     * @returns {Plugin[]}
+     */
+    createPluginInstances(): Plugin[];
+    /**
+     *
+     * @param {string} cmd
+     * @param  {...any} args
+     * @returns {Promise<{value: any, error?: Error, protocol: string} | import('type-fest').AsyncReturnType<ExternalDriver['executeCommand']>>}
+     */
+    executeCommand(cmd: string, ...args: any[]): Promise<any>;
+    wrapCommandWithPlugins({ driver, cmd, args, next, cmdHandledBy, plugins }: {
+        driver: any;
+        cmd: any;
+        args: any;
+        next: any;
+        cmdHandledBy: any;
+        plugins: any;
+    }): any;
+    logPluginHandlerReport(plugins: any, { cmd, cmdHandledBy }: {
+        cmd: any;
+        cmdHandledBy: any;
+    }): void;
+    executeWrappedCommand({ wrappedCmd, protocol }: {
+        wrappedCmd: any;
+        protocol: any;
+    }): Promise<{
+        value: any;
+        error: any;
+        protocol: any;
+    }>;
+    proxyActive(sessionId: any): boolean;
+    canProxy(sessionId: any): boolean;
+}
+declare namespace desiredCapabilityConstraints {
+    namespace automationName {
+        const presence: true;
+        const isString: true;
+    }
+    namespace platformName {
+        const presence_1: true;
+        export { presence_1 as presence };
+        const isString_1: true;
+        export { isString_1 as isString };
+    }
+}
+import { DriverCore } from "@appium/base-driver";
+export {};
+//# sourceMappingURL=appium.d.ts.map

package/build/lib/appium.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"appium.d.ts","sourceRoot":"","sources":["../../lib/appium.js"],"names":[],"mappings":"AAkzBA;;;GAGG;AACH;IAME,cAOC;IAZD;;OAEG;IACH,MAFU,SAAS,MAAM,CAAC,CAEgB;CAU3C;yBAKY,OAAO,eAAe,EAAE,UAAU;yBAClC,OAAO,eAAe,EAAE,UAAU;0BAClC,OAAO,eAAe,EAAE,WAAW;2BACnC,OAAO,eAAe,EAAE,YAAY;4BACpC,OAAO,eAAe,EAAE,aAAa;2BACrC,OAAO,2BAA2B,EAAE,YAAY;yBAChD,OAAO,eAAe,EAAE,UAAU;yBAClC,OAAO,eAAe,EAAE,UAAU;2BAClC,OAAO,eAAe,EAAE,YAAY;6BACpC,OAAO,eAAe,EAAE,cAAc;0BACtC,OAAO,eAAe,EAAE,WAAW;qBACnC,OAAO,eAAe,EAAE,MAAM;0BAC9B,OAAO,eAAe,EAAE,WAAW,CAAC,OAAO,eAAe,EAAE,MAAM,CAAC;mCAInE,OAAO,eAAe,EAAE,eAAe,CAAC,uBAAuB,EAC3E,0BAA4B,EAAE,0BAA0B,CAAC;yCAI7C,qBAAqB;IAAC,cAAc,EAAE,MAAM;IAAE,IAAI,EAC9D,OAAS,eAAe,EAAE,UAAU,CAAC,WAAW,CAAC;IAAE,QAAQ,EAAE,MAAM,GAAC,SAAS;CAAC,CAAC;kEAKnE,OAAO,eAAe,EAAE,IAAI,CAAC,CAAC,CAAC;yCAI/B,qBAAqB,IAAI,CAAC;;;;;;;;;;sCAc1B,mCAAmC;kCACnC,OAAO,eAAe,EAAE,aAAa,CAAC,uBAAuB,CAAC;AAr1B3E;;GAEG;AACH;;;;;;;;;;IAyDE;;OAEG;IACH,kBAFW,OAAO,eAAe,EAAE,UAAU,CAAC,uBAAuB,CAAC,EA+BrE;IAxFD;;;;;OAKG;IACH,UAFU,OAAO,MAAM,EAAC,cAAc,CAAC,CAE9B;IAET;;;;;OAKG;IACH,gBAFU,OAAO,MAAM,EAAC,cAAc,EAAE,CAAC,CAE1B;IASf;;;OAGG;IACH,eAFU,IAAI,WAAW,EAAC,MAAM,CAAC,CAEnB;IAEd;;;OAGG;IACH,gBAFU,OAAO,MAAM,EAAC,aAAa,WAAW,CAAC,EAAE,CAAC,CAErC;IAEf;;;OAGG;IACH,oBAFU,aAAa,WAAW,CAAC,EAAE,CAElB;IAEnB,2BAA2B;IAC3B,cADW,YAAY,CACV;IAEb,2BAA2B;IAC3B,QADW,YAAY,CAChB;IAEP;;;OAGG;IACH,gCAHU,uBAAuB,CAGX;IAEtB,0EAA0E;IAC1E,MADW,OAAO,eAAe,EAAE,UAAU,CAAC,uBAAuB,CAAC,CACjE;IAsDL,uCAGC;IAED,sHAEC;IAGD;;OAIC;IAED;;;SAKC;IAED,+FAiBC;IAED;;;;OAIG;IACH,6BAHW,MAAM,GACJ,YAAY,CAIxB;IAED;;;;;;;;OAQG;IACH,6BAHW,MAAM,GACJ,YAAY,GAAC,SAAS,CAclC;IAED;;;;;;OAMG;IACH,0BALW,mBAAmB,iGAGjB,QAAQ,0BAA0B,CAAC,CAyK/C;IAED;;;;OAIG;IACH,wCAHW,cAAc,kBACd,MAAM,QAsChB;IAED;;;;;;OAMG;IACH,gDALsB,GAAG,EAAE,KAAK,GAAG,mBAAgB,GAAG,EAAE,KAAK,GAAG,IACnD,QAAQ,UAAU,EAAE,CAAC,CAmBjC;IAED;;OAEG;IACH,yBAFW,MAAM;;;;;;;;OA0ChB;IAED,4CAqBC;IAED;;;;;OAKG;IACH,8BAHY,MAAM,gBAejB;IAED;;;;;;;;;OASG;IACH,wBAJW,MAAM,cACL,MAAM,gBASjB;IAED;;;OAGG;IACH,yBAFa,MAAM,EAAE,CAWpB;IAED;;;;;OAKG;IACH,oBAJW,MAAM,WACF,GAAG,kBAgIjB;IAED;;;;;;;YAwBC;IAED;;;aAoBC;IAED;;;;;;;OAwBC;IAED,qCAGC;IAYD,kCAGC;CACF"}