cloud-ide-element 1.1.238 → 1.1.239

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/index.d.ts CHANGED
@@ -616,7 +616,7 @@ declare class CideEleFileInputComponent implements ControlValueAccessor, OnDestr
616
616
  readonly id: _angular_core.WritableSignal<string>;
617
617
  readonly isUploading: _angular_core.WritableSignal<boolean>;
618
618
  readonly uploadProgress: _angular_core.WritableSignal<number>;
619
- readonly uploadStatus: _angular_core.WritableSignal<"success" | "error" | "start" | "uploading" | "idle">;
619
+ readonly uploadStatus: _angular_core.WritableSignal<"error" | "start" | "uploading" | "success" | "idle">;
620
620
  readonly files: _angular_core.WritableSignal<FileList | null>;
621
621
  readonly fileNames: _angular_core.WritableSignal<string[]>;
622
622
  readonly previewUrls: _angular_core.WritableSignal<string[]>;
@@ -753,7 +753,7 @@ declare class CideEleFileInputComponent implements ControlValueAccessor, OnDestr
753
753
  multiple: boolean;
754
754
  showPreview: boolean;
755
755
  autoUpload: boolean;
756
- uploadStatus: "success" | "error" | "start" | "uploading" | "idle";
756
+ uploadStatus: "error" | "start" | "uploading" | "success" | "idle";
757
757
  isUploading: boolean;
758
758
  uploadProgress: number;
759
759
  files: {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "cloud-ide-element",
3
- "version": "1.1.238",
3
+ "version": "1.1.239",
4
4
  "peerDependencies": {
5
5
  "@angular/common": "^20.1.0",
6
6
  "@angular/core": "^20.1.0"
package/README.md DELETED
@@ -1,63 +0,0 @@
1
- # CloudIdeElement
2
-
3
- This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 20.1.0.
4
-
5
- ## Code scaffolding
6
-
7
- Angular CLI includes powerful code scaffolding tools. To generate a new component, run:
8
-
9
- ```bash
10
- ng generate component component-name
11
- ```
12
-
13
- For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:
14
-
15
- ```bash
16
- ng generate --help
17
- ```
18
-
19
- ## Building
20
-
21
- To build the library, run:
22
-
23
- ```bash
24
- ng build cloud-ide-element
25
- ```
26
-
27
- This command will compile your project, and the build artifacts will be placed in the `dist/` directory.
28
-
29
- ### Publishing the Library
30
-
31
- Once the project is built, you can publish your library by following these steps:
32
-
33
- 1. Navigate to the `dist` directory:
34
- ```bash
35
- cd dist/cloud-ide-element
36
- ```
37
-
38
- 2. Run the `npm publish` command to publish your library to the npm registry:
39
- ```bash
40
- npm publish
41
- ```
42
-
43
- ## Running unit tests
44
-
45
- To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:
46
-
47
- ```bash
48
- ng test
49
- ```
50
-
51
- ## Running end-to-end tests
52
-
53
- For end-to-end (e2e) testing, run:
54
-
55
- ```bash
56
- ng e2e
57
- ```
58
-
59
- Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.
60
-
61
- ## Additional Resources
62
-
63
- For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.