@dataloop-ai/components 0.13.16 → 0.13.18

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dataloop-ai/components",
-  "version": "0.13.16",
+  "version": "0.13.18",
   "exports": {
     ".": "./index.ts",
     "./models": "./models.ts",

package/src/components/DlDialogBox/DlDialogBox.vue

@@ -18,6 +18,7 @@
                 }"
                 :class="{
                     'dialog-wrapper--fullscreen': fullscreen,
+                    'dialog-wrapper--fullheight': fullHeight,
                     'dialog-wrapper--right': position === 'right',
                     'dialog-wrapper--left': position === 'left'
                 }"
@@ -30,7 +31,10 @@
                 </div>
                 <div
                     class="content"
-                    :class="{ 'content--fullscreen': fullscreen }"
+                    :class="{
+                        'content--fullscreen': fullscreen,
+                        'content--fullheight': fullHeight
+                    }"
                 >
                     <slot name="body" />
                 </div>
@@ -59,6 +63,7 @@ export default defineComponent({
         width: { type: [Number, String], default: 400 },
         height: { type: [Number, String], default: 'fit-content' },
         fullscreen: Boolean,
+        fullHeight: Boolean,
         separators: { type: Boolean, default: true },
         position: {
             type: String as PropType<'left' | 'right' | 'center'>,
@@ -178,6 +183,11 @@ export default defineComponent({
         height: 100vh !important;
         border-radius: 0px;
     }
+    &--fullheight {
+        margin: 0;
+        height: 100vh !important;
+        border-radius: 0px;
+    }
     &--right {
         position: absolute !important;
         right: 0;
@@ -202,6 +212,9 @@ export default defineComponent({
     &--fullscreen {
         flex-grow: 1 !important;
     }
+    &--fullheight {
+        flex-grow: 1 !important;
+    }
 }
 
 .footer {

package/CODE_OF_CONDUCT.md

@@ -1,36 +0,0 @@
-# Code of Conduct
-
-## Our Pledge
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-#### Examples of behavior that contributes to creating a positive environment include:
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
-
-#### Examples of unacceptable behavior by participants include:
-- The use of sexualized language or imagery and unwelcome sexual attention or advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Our Responsibilities
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-
-## Scope
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
-
-## Enforcement
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at support@dataloop.ai . All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
-
-## Attribution
-This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

package/CONTRIBUTION.md

@@ -1,47 +0,0 @@
-# Contributing Guidelines
-Thank you for your interest in contributing to our project! We welcome contributions from everyone. Please take a moment to review these guidelines before submitting a pull request or issue.
-
-## Code of Conduct
-Our project has a [Code of Conduct](./CODE_OF_CONDUCT.md) that we expect all contributors to follow. Please read it before making any contribution.
-
-## Issues
-If you find any issues or bugs, please search the existing issues to see if the issue has already been reported. If it hasn't, please create a new issue with a clear and concise title and description. Be sure to include any relevant information, such as error messages or steps to reproduce the issue.
-
-The repository provides base templates for create a bug/feature request type of issues. please fill the relevant information there.
-
-If the issue is related to a specific component then please have in the title of the issue the name of the component and then a short description of the issue. Example: ``` DlButton > 'description of issue' ```
-
-## Pull Requests
-We welcome contributions in the form of pull requests. Before submitting a pull request, please make sure that your code:
-
-- Is well-tested
-- Conforms to our coding style guidelines (see below)
-- Includes any necessary documentation
-
-### Naming Convention
-Each pull request should reflect the issue it is trying to close or have a short descriptive title.
-
-If the pull request is working on a specific component please start the pull request title with the components name. Example: ``` DlButton > 'description of issue' ```
-
-### Coding Style Guidelines
-Please follow these coding style guidelines when submitting a pull request:
-- Use consistent indentation
-- Use descriptive variable names
-- Use comments to explain non-obvious code behavior
-- Follow the provided linter configuration
-    - Please note that any build that does not pass the linter will fail. as part of our CI/CD
-
-
-Steps to submit a pull request:
-1. Fork the repository
-2. Clone the forked repository to your local machine
-3. Create a new branch for your changes
-4. Make your changes and commit them
-5. Push the changes to your forked repository
-6. Submit a pull request to the original repository
-7. Please make sure that your pull request clearly explains the problem you are trying to solve, the solution you have implemented, and any potential side effects of your changes.
-
-## License
-By contributing to our project, you agree that your contributions will be licensed under the [project's license](./LICENSE.md).
-
-Thank you for your contributions!