You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CODE_OF_CONDUCT.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,19 +10,19 @@ We pledge to act and interact in ways that contribute to an open, welcoming, div
10
10
11
11
Examples of behavior that contributes to a positive environment for our community include:
12
12
13
-
* Demonstrating empathy and kindness toward other people
14
-
* Being respectful of differing opinions, viewpoints, and experiences
15
-
* Giving and gracefully accepting constructive feedback
16
-
* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
17
-
* Focusing on what is best not just for us as individuals, but for the overall community
13
+
- Demonstrating empathy and kindness toward other people
14
+
- Being respectful of differing opinions, viewpoints, and experiences
15
+
- Giving and gracefully accepting constructive feedback
16
+
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
17
+
- Focusing on what is best not just for us as individuals, but for the overall community
18
18
19
19
Examples of unacceptable behavior include:
20
20
21
-
* The use of sexualized language or imagery, and sexual attention or advances of any kind
22
-
* Trolling, insulting or derogatory comments, and personal or political attacks
23
-
* Public or private harassment
24
-
* Publishing others' private information, such as a physical or email address, without their explicit permission
25
-
* Other conduct which can reasonably be considered inappropriate in a professional setting
21
+
- The use of sexualized language or imagery, and sexual attention or advances of any kind
22
+
- Trolling, insulting or derogatory comments, and personal or political attacks
23
+
- Public or private harassment
24
+
- Publishing others' private information, such as a physical or email address, without their explicit permission
25
+
- Other conduct which can reasonably be considered inappropriate in a professional setting
26
26
27
27
## Enforcement Responsibilities
28
28
@@ -67,4 +67,4 @@ Community leaders will follow these Community Impact Guidelines in determining t
67
67
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+21-21Lines changed: 21 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,20 +28,20 @@ This project adheres to the [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md). By partici
28
28
29
29
If you find a bug, please open an issue on our [GitHub Issues page](https://github.com/interactive-video-labs/interactive-video-vue-wrapper/issues). When reporting a bug, please include:
- Your environment (Vue version, browser, OS, etc.).
37
37
38
38
### Suggesting Enhancements
39
39
40
40
If you have an idea for a new feature or an improvement, please open an issue on our [GitHub Issues page](https://github.com/interactive-video-labs/interactive-video-vue-wrapper/issues). When suggesting an enhancement, please include:
41
41
42
-
-A clear and concise description of the proposed enhancement.
43
-
-The problem it solves or the benefit it provides.
44
-
-Any alternative solutions you've considered.
42
+
- A clear and concise description of the proposed enhancement.
43
+
- The problem it solves or the benefit it provides.
44
+
- Any alternative solutions you've considered.
45
45
46
46
### Your First Code Contribution
47
47
@@ -68,9 +68,9 @@ If you're looking to make your first code contribution, look for issues labeled
68
68
69
69
In your pull request description, please:
70
70
71
-
- Reference any related issues (e.g., `Fixes #123`, `Closes #456`).
72
-
- Provide a clear explanation of your changes.
73
-
- Include screenshots or GIFs if your changes affect the UI.
71
+
- Reference any related issues (e.g., `Fixes #123`, `Closes #456`).
72
+
- Provide a clear explanation of your changes.
73
+
- Include screenshots or GIFs if your changes affect the UI.
74
74
75
75
## Development Setup
76
76
@@ -82,18 +82,18 @@ For detailed instructions on setting up your development environment, installing
82
82
83
83
We follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification for our commit messages. This helps with automated changelog generation and semantic versioning. Examples:
84
84
85
-
- `feat: add new video playback controls`
86
-
- `fix: resolve autoplay issue on iOS`
87
-
- `docs: update installation instructions`
88
-
- `refactor: improve player initialization logic`
89
-
- `test: add unit tests for cue points`
85
+
- `feat: add new video playback controls`
86
+
- `fix: resolve autoplay issue on iOS`
87
+
- `docs: update installation instructions`
88
+
- `refactor: improve player initialization logic`
89
+
- `test: add unit tests for cue points`
90
90
91
91
### TypeScript Styleguide
92
92
93
-
- Follow existing code style and formatting.
94
-
- Use clear and descriptive variable and function names.
95
-
- Ensure proper type annotations for all functions, variables, and parameters.
96
-
- Avoid `any` type unless absolutely necessary.
93
+
- Follow existing code style and formatting.
94
+
- Use clear and descriptive variable and function names.
95
+
- Ensure proper type annotations for all functions, variables, and parameters.
@@ -26,35 +27,35 @@ To get started with local development, follow these steps:
26
27
27
28
Here are the common development scripts available:
28
29
29
-
- **`pnpm build`**: Compiles the TypeScript source code into JavaScript (ESM and CommonJS formats) and generates declaration files (`.d.ts`). This command is run before publishing.
30
+
- **`pnpm build`**: Compiles the TypeScript source code into JavaScript (ESM and CommonJS formats) and generates declaration files (`.d.ts`). This command is run before publishing.
30
31
31
-
```bash
32
-
pnpm build
33
-
```
32
+
```bash
33
+
pnpm build
34
+
```
34
35
35
-
- **`pnpm dev`**: Starts the TypeScript compiler in watch mode, recompiling files on changes. Useful for active development.
36
+
- **`pnpm dev`**: Starts the TypeScript compiler in watch mode, recompiling files on changes. Useful for active development.
36
37
37
-
```bash
38
-
pnpm dev
39
-
```
38
+
```bash
39
+
pnpm dev
40
+
```
40
41
41
-
- **`pnpm test`**: Runs the unit tests using Vitest.
42
+
- **`pnpm test`**: Runs the unit tests using Vitest.
42
43
43
-
```bash
44
-
pnpm test
45
-
```
44
+
```bash
45
+
pnpm test
46
+
```
46
47
47
-
- **`pnpm clean`**: Removes the `dist` directory, clearing all compiled output.
48
+
- **`pnpm clean`**: Removes the `dist` directory, clearing all compiled output.
48
49
49
-
```bash
50
-
pnpm clean
51
-
```
50
+
```bash
51
+
pnpm clean
52
+
```
52
53
53
-
- **`pnpm prepare`**: This script is typically run after `pnpm install` and before `pnpm publish`. In this project, it simply runs `pnpm build`.
54
+
- **`pnpm prepare`**: This script is typically run after `pnpm install` and before `pnpm publish`. In this project, it simply runs `pnpm build`.
|`videoUrl`|`string`|`true`| - | The URL of the video to be loaded.|
90
-
|`cues`|`CuePoint[]`|`false`|`[]`| An array of cue points for interactive events. Can be updated dynamically.|
91
-
|`translations`|`Translations`|`false`|`{}`| An object containing translations for the player UI.|
92
-
|`onAnalyticsEvent`|`(event: AnalyticsEvent, payload?: AnalyticsPayload) => void`|`false`| - | Callback function for analytics events emitted by the player.|
93
-
|`autoplay`|`boolean`|`false`|`false`| Whether the video should start playing automatically.|
94
-
|`loop`|`boolean`|`false`|`false`| Whether the video should loop.|
95
-
|`locale`|`string`|`false`|`'en'`| The locale to be used for the player (e.g., 'en', 'es').|
|`videoUrl`|`string`|`true`| - | The URL of the video to be loaded. |
91
+
|`cues`|`CuePoint[]`|`false`|`[]`| An array of cue points for interactive events. Can be updated dynamically. |
92
+
|`translations`|`Translations`|`false`|`{}`| An object containing translations for the player UI. |
93
+
|`onAnalyticsEvent`|`(event: AnalyticsEvent, payload?: AnalyticsPayload) => void`|`false`| - | Callback function for analytics events emitted by the player. |
94
+
|`autoplay`|`boolean`|`false`|`false`| Whether the video should start playing automatically. |
95
+
|`loop`|`boolean`|`false`|`false`| Whether the video should loop. |
96
+
|`locale`|`string`|`false`|`'en'`| The locale to be used for the player (e.g., 'en', 'es'). |
96
97
97
98
Any additional attributes passed to the component will be forwarded to the underlying `@interactive-video-labs/core` player configuration.
0 commit comments