immosquare-cleaner 0.1.38 → 0.1.39

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 826f3aa2e653950168ccbbb34157ad1096e6a9e70f2c017e5bd3081ab7757114
-  data.tar.gz: b2363325006e03329f63de37f1c62801f8bc57ca4570511fb367e4dfd80869ac
+  metadata.gz: 662eeb40e52c560a97f249cb9a4e5b3d1d80285e8391c60f719028e2cc3d89ce
+  data.tar.gz: ef9f7f751deaa0921133beed9c05bcd0c641efa68cef3fe6f6a1fe760201e21e
 SHA512:
-  metadata.gz: 1a0f7f2846f19cac93d25f63d29527e6eb9297fda94e1a0058e45abbee950c447f97f354ad79f5ba85da58aac0e8f2afaa5003c1c45f21bbea38e4aca58b3b59
-  data.tar.gz: '09aed90bad520d075dd1b951f5654df5c97f053776d8f7b3dc62668eac92fbb190061d1b6313b629320bb85cd9b2b24c50a97071a7ca24a16c271b1f91275697'
+  metadata.gz: 943bde00627ece2cf5df78f727473c73fa501d21adf0fa433c3a8f59d62625530f4dbeab2e4d5ff27be15bad2cc52d6b578a158d7ccc63b7a4b0657019c4263d
+  data.tar.gz: fdb856a0c4deb5f4aabef0182f9fb1944cdfbd6526aa16650369d8bf61e519775200d1d227bfd08fe104a11ec7cda5135296bc1377d83f116c9e600499a219d7

data/lib/immosquare-cleaner/version.rb

@@ -1,3 +1,3 @@
 module ImmosquareCleaner
-  VERSION = "0.1.38".freeze
+  VERSION = "0.1.39".freeze
 end

data/node_modules/@eslint/config-array/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/node_modules/@eslint/config-array/README.md

@@ -0,0 +1,340 @@
+# Config Array
+
+## Description
+
+A config array is a way of managing configurations that are based on glob pattern matching of filenames. Each config array contains the information needed to determine the correct configuration for any file based on the filename.
+
+**Note:** This is a generic package that can be used outside of ESLint. It contains no ESLint-specific functionality.
+
+## Installation
+
+For Node.js and compatible runtimes:
+
+```shell
+npm install @eslint/config-array
+# or
+yarn add @eslint/config-array
+# or
+pnpm install @eslint/config-array
+# or
+bun install @eslint/config-array
+```
+
+For Deno:
+
+```shell
+deno add @eslint/config-array
+```
+
+## Background
+
+The basic idea is that all configuration, including overrides, can be represented by a single array where each item in the array is a config object. Config objects appearing later in the array override config objects appearing earlier in the array. You can calculate a config for a given file by traversing all config objects in the array to find the ones that match the filename. Matching is done by specifying glob patterns in `files` and `ignores` properties on each config object. Here's an example:
+
+```js
+export default [
+	// match all JSON files
+	{
+		name: "JSON Handler",
+		files: ["**/*.json"],
+		handler: jsonHandler,
+	},
+
+	// match only package.json
+	{
+		name: "package.json Handler",
+		files: ["package.json"],
+		handler: packageJsonHandler,
+	},
+];
+```
+
+In this example, there are two config objects: the first matches all JSON files in all directories and the second matches just `package.json` in the base path directory (all the globs are evaluated as relative to a base path that can be specified). When you retrieve a configuration for `foo.json`, only the first config object matches so `handler` is equal to `jsonHandler`; when you retrieve a configuration for `package.json`, `handler` is equal to `packageJsonHandler` (because both config objects match, the second one wins).
+
+## Usage
+
+First, import the `ConfigArray` constructor:
+
+```js
+import { ConfigArray } from "@eslint/config-array";
+
+// or using CommonJS
+
+const { ConfigArray } = require("@eslint/config-array");
+```
+
+When you create a new instance of `ConfigArray`, you must pass in two arguments: an array of configs and an options object. The array of configs is most likely read in from a configuration file, so here's a typical example:
+
+```js
+const configFilename = path.resolve(process.cwd(), "my.config.js");
+const { default: rawConfigs } = await import(configFilename);
+const configs = new ConfigArray(rawConfigs, {
+	// the path to match filenames from
+	basePath: process.cwd(),
+
+	// additional items in each config
+	schema: mySchema,
+});
+```
+
+This example reads in an object or array from `my.config.js` and passes it into the `ConfigArray` constructor as the first argument. The second argument is an object specifying the `basePath` (the directory in which `my.config.js` is found) and a `schema` to define the additional properties of a config object beyond `files`, `ignores`, and `name`.
+
+### Specifying a Schema
+
+The `schema` option is required for you to use additional properties in config objects. The schema is an object that follows the format of an [`ObjectSchema`](https://npmjs.com/package/@eslint/object-schema). The schema specifies both validation and merge rules that the `ConfigArray` instance needs to combine configs when there are multiple matches. Here's an example:
+
+```js
+const configFilename = path.resolve(process.cwd(), "my.config.js");
+const { default: rawConfigs } = await import(configFilename);
+
+const mySchema = {
+
+    // define the handler key in configs
+    handler: {
+        required: true,
+        merge(a, b) {
+            if (!b) return a;
+            if (!a) return b;
+        },
+        validate(value) {
+            if (typeof value !== "function") {
+                throw new TypeError("Function expected.");
+            }
+        }
+    }
+};
+
+const configs = new ConfigArray(rawConfigs, {
+
+    // the path to match filenames from
+    basePath: process.cwd(),
+
+    // additional item schemas in each config
+    schema: mySchema,
+
+    // additional config types supported (default: [])
+    extraConfigTypes: ["array", "function"];
+});
+```
+
+### Config Arrays
+
+Config arrays can be multidimensional, so it's possible for a config array to contain another config array when `extraConfigTypes` contains `"array"`, such as:
+
+```js
+export default [
+	// JS config
+	{
+		files: ["**/*.js"],
+		handler: jsHandler,
+	},
+
+	// JSON configs
+	[
+		// match all JSON files
+		{
+			name: "JSON Handler",
+			files: ["**/*.json"],
+			handler: jsonHandler,
+		},
+
+		// match only package.json
+		{
+			name: "package.json Handler",
+			files: ["package.json"],
+			handler: packageJsonHandler,
+		},
+	],
+
+	// filename must match function
+	{
+		files: [filePath => filePath.endsWith(".md")],
+		handler: markdownHandler,
+	},
+
+	// filename must match all patterns in subarray
+	{
+		files: [["*.test.*", "*.js"]],
+		handler: jsTestHandler,
+	},
+
+	// filename must not match patterns beginning with !
+	{
+		name: "Non-JS files",
+		files: ["!*.js"],
+		settings: {
+			js: false,
+		},
+	},
+];
+```
+
+In this example, the array contains both config objects and a config array. When a config array is normalized (see details below), it is flattened so only config objects remain. However, the order of evaluation remains the same.
+
+If the `files` array contains a function, then that function is called with the absolute path of the file and is expected to return `true` if there is a match and `false` if not. (The `ignores` array can also contain functions.)
+
+If the `files` array contains an item that is an array of strings and functions, then all patterns must match in order for the config to match. In the preceding examples, both `*.test.*` and `*.js` must match in order for the config object to be used.
+
+If a pattern in the files array begins with `!` then it excludes that pattern. In the preceding example, any filename that doesn't end with `.js` will automatically get a `settings.js` property set to `false`.
+
+You can also specify an `ignores` key that will force files matching those patterns to not be included. If the `ignores` key is in a config object without any other keys, then those ignores will always be applied; otherwise those ignores act as exclusions. Here's an example:
+
+```js
+export default [
+
+    // Always ignored
+    {
+        ignores: ["**/.git/**", "**/node_modules/**"]
+    },
+
+    // .eslintrc.js file is ignored only when .js file matches
+    {
+        files: ["**/*.js"],
+        ignores: [".eslintrc.js"]
+        handler: jsHandler
+    }
+];
+```
+
+You can use negated patterns in `ignores` to exclude a file that was already ignored, such as:
+
+```js
+export default [
+	// Ignore all JSON files except tsconfig.json
+	{
+		files: ["**/*"],
+		ignores: ["**/*.json", "!tsconfig.json"],
+	},
+];
+```
+
+### Config Functions
+
+Config arrays can also include config functions when `extraConfigTypes` contains `"function"`. A config function accepts a single parameter, `context` (defined by you), and must return either a config object or a config array (it cannot return another function). Config functions allow end users to execute code in the creation of appropriate config objects. Here's an example:
+
+```js
+export default [
+	// JS config
+	{
+		files: ["**/*.js"],
+		handler: jsHandler,
+	},
+
+	// JSON configs
+	function (context) {
+		return [
+			// match all JSON files
+			{
+				name: context.name + " JSON Handler",
+				files: ["**/*.json"],
+				handler: jsonHandler,
+			},
+
+			// match only package.json
+			{
+				name: context.name + " package.json Handler",
+				files: ["package.json"],
+				handler: packageJsonHandler,
+			},
+		];
+	},
+];
+```
+
+When a config array is normalized, each function is executed and replaced in the config array with the return value.
+
+**Note:** Config functions can also be async.
+
+### Normalizing Config Arrays
+
+Once a config array has been created and loaded with all of the raw config data, it must be normalized before it can be used. The normalization process goes through and flattens the config array as well as executing all config functions to get their final values.
+
+To normalize a config array, call the `normalize()` method and pass in a context object:
+
+```js
+await configs.normalize({
+	name: "MyApp",
+});
+```
+
+The `normalize()` method returns a promise, so be sure to use the `await` operator. The config array instance is normalized in-place, so you don't need to create a new variable.
+
+If you want to disallow async config functions, you can call `normalizeSync()` instead. This method is completely synchronous and does not require using the `await` operator as it does not return a promise:
+
+```js
+await configs.normalizeSync({
+	name: "MyApp",
+});
+```
+
+**Important:** Once a `ConfigArray` is normalized, it cannot be changed further. You can, however, create a new `ConfigArray` and pass in the normalized instance to create an unnormalized copy.
+
+### Getting Config for a File
+
+To get the config for a file, use the `getConfig()` method on a normalized config array and pass in the filename to get a config for:
+
+```js
+// pass in absolute filename
+const fileConfig = configs.getConfig(
+	path.resolve(process.cwd(), "package.json"),
+);
+```
+
+The config array always returns an object, even if there are no configs matching the given filename. You can then inspect the returned config object to determine how to proceed.
+
+A few things to keep in mind:
+
+-   You must pass in the absolute filename to get a config for.
+-   The returned config object never has `files`, `ignores`, or `name` properties; the only properties on the object will be the other configuration options specified.
+-   The config array caches configs, so subsequent calls to `getConfig()` with the same filename will return in a fast lookup rather than another calculation.
+-   A config will only be generated if the filename matches an entry in a `files` key. A config will not be generated without matching a `files` key (configs without a `files` key are only applied when another config with a `files` key is applied; configs without `files` are never applied on their own). Any config with a `files` key entry ending with `/**` or `/*` will only be applied if another entry in the same `files` key matches or another config matches.
+
+## Determining Ignored Paths
+
+You can determine if a file is ignored by using the `isFileIgnored()` method and passing in the absolute path of any file, as in this example:
+
+```js
+const ignored = configs.isFileIgnored("/foo/bar/baz.txt");
+```
+
+A file is considered ignored if any of the following is true:
+
+-   **It's parent directory is ignored.** For example, if `foo` is in `ignores`, then `foo/a.js` is considered ignored.
+-   **It has an ancestor directory that is ignored.** For example, if `foo` is in `ignores`, then `foo/baz/a.js` is considered ignored.
+-   **It matches an ignored file pattern.** For example, if `**/a.js` is in `ignores`, then `foo/a.js` and `foo/baz/a.js` are considered ignored.
+-   **If it matches an entry in `files` and also in `ignores`.** For example, if `**/*.js` is in `files` and `**/a.js` is in `ignores`, then `foo/a.js` and `foo/baz/a.js` are considered ignored.
+-   **The file is outside the `basePath`.** If the `basePath` is `/usr/me`, then `/foo/a.js` is considered ignored.
+
+For directories, use the `isDirectoryIgnored()` method and pass in the absolute path of any directory, as in this example:
+
+```js
+const ignored = configs.isDirectoryIgnored("/foo/bar/");
+```
+
+A directory is considered ignored if any of the following is true:
+
+-   **It's parent directory is ignored.** For example, if `foo` is in `ignores`, then `foo/baz` is considered ignored.
+-   **It has an ancestor directory that is ignored.** For example, if `foo` is in `ignores`, then `foo/bar/baz/a.js` is considered ignored.
+-   **It matches and ignored file pattern.** For example, if `**/a.js` is in `ignores`, then `foo/a.js` and `foo/baz/a.js` are considered ignored.
+-   **If it matches an entry in `files` and also in `ignores`.** For example, if `**/*.js` is in `files` and `**/a.js` is in `ignores`, then `foo/a.js` and `foo/baz/a.js` are considered ignored.
+-   **The file is outside the `basePath`.** If the `basePath` is `/usr/me`, then `/foo/a.js` is considered ignored.
+
+**Important:** A pattern such as `foo/**` means that `foo` and `foo/` are _not_ ignored whereas `foo/bar` is ignored. If you want to ignore `foo` and all of its subdirectories, use the pattern `foo` or `foo/` in `ignores`.
+
+## Caching Mechanisms
+
+Each `ConfigArray` aggressively caches configuration objects to avoid unnecessary work. This caching occurs in two ways:
+
+1. **File-based Caching.** For each filename that is passed into a method, the resulting config is cached against that filename so you're always guaranteed to get the same object returned from `getConfig()` whenever you pass the same filename in.
+2. **Index-based Caching.** Whenever a config is calculated, the config elements that were used to create the config are also cached. So if a given filename matches elements 1, 5, and 7, the resulting config is cached with a key of `1,5,7`. That way, if another file is passed that matches the same config elements, the result is already known and doesn't have to be recalculated. That means two files that match all the same elements will return the same config from `getConfig()`.
+
+## Acknowledgements
+
+The design of this project was influenced by feedback on the ESLint RFC, and incorporates ideas from:
+
+-   Teddy Katz (@not-an-aardvark)
+-   Toru Nagashima (@mysticatea)
+-   Kai Cataldo (@kaicataldo)
+
+## License
+
+Apache 2.0