@qoretechnologies/reqore 0.30.6 → 0.30.8

package/CODE_OF_CONDUCT.md

@@ -1,105 +1,105 @@
-<div align="center">
-  <br><br><br>
-  <img src="./public/qoreLogo.png" alt="Unstated Logo" width="500">
-  <br><br><br>
-</div>
-
-# Code of Conduct
-
-Qore Technologies use [Contributor Covenant v2.0](https://contributor-covenant.org/version/2/0/code_of_conduct) as their code of conduct. The full text is included [below](#contributor-covenant-code-of-conduct-v20) in English, and [translations](https://www.contributor-covenant.org/translations) are available on the Contributor Covenant website.
-
-## Commitment
-
-All recipients of reports commit to:
-
-- maintain the confidentiality with regard to the reporter and victim of an incident
-
-## Report an issue in a project
-
-1. To report an issue in one of our projects, please follow the security guidelines from that repository.
-
-## More Info
-
-For more information, refer to the full
-[Contributor covenant code of conduct page](https://contributor-covenant.org/version/2/0/code_of_conduct).
-
----
-
-## Contributor Covenant Code of Conduct v2.0
-
-### Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
-
-### Our Standards
-
-Examples of behavior that contributes to a positive environment for our community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-### Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
-
-Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
-
-### Scope
-
-This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official 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 to the community leaders responsible for enforcement at the email addresses listed above in the [Reporting](#report-an-issue-in-a-project) and [Escalation](#escalate-an-issue) sections. All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the reporter of any incident.
-
-### Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
-
-#### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
-
-#### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
-
-#### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
-
-#### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the project community.
-
-### Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0, available at [contributor-covenant.org/version/2/0/code_of_conduct](https://www.contributor-covenant.org/version/2/0/code_of_conduct).
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
-
-For answers to common questions about this code of conduct, see the FAQ at
+<div align="center">
+  <br><br><br>
+  <img src="./public/qoreLogo.png" alt="Unstated Logo" width="500">
+  <br><br><br>
+</div>
+
+# Code of Conduct
+
+Qore Technologies use [Contributor Covenant v2.0](https://contributor-covenant.org/version/2/0/code_of_conduct) as their code of conduct. The full text is included [below](#contributor-covenant-code-of-conduct-v20) in English, and [translations](https://www.contributor-covenant.org/translations) are available on the Contributor Covenant website.
+
+## Commitment
+
+All recipients of reports commit to:
+
+- maintain the confidentiality with regard to the reporter and victim of an incident
+
+## Report an issue in a project
+
+1. To report an issue in one of our projects, please follow the security guidelines from that repository.
+
+## More Info
+
+For more information, refer to the full
+[Contributor covenant code of conduct page](https://contributor-covenant.org/version/2/0/code_of_conduct).
+
+---
+
+## Contributor Covenant Code of Conduct v2.0
+
+### Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+### Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+### Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
+
+### Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official 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 to the community leaders responsible for enforcement at the email addresses listed above in the [Reporting](#report-an-issue-in-a-project) and [Escalation](#escalate-an-issue) sections. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+### Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+#### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+#### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+#### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+#### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the project community.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0, available at [contributor-covenant.org/version/2/0/code_of_conduct](https://www.contributor-covenant.org/version/2/0/code_of_conduct).
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at
 [contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are available at [contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).

package/CONTRIBUTING.MD

@@ -1,78 +1,78 @@
-<div align="center">
-  <br><br><br>
-  <img src="./public/qoreLogo.png" alt="Unstated Logo" width="500">
-  <br><br><br>
-</div>
-
-# Contributing to Qore Technologies
-
-> First off, thanks for taking the time to contribute!
-
-Contributions are always welcome. Before contributing please read the
-[code of conduct](CODE_OF_CONDUCT.md) &
-[search the issue tracker](https://github.com/qoretechnologies/qorus-ui/issues) your issue may have already been discussed or fixed in `master`. To contribute,
-[fork](https://help.github.com/articles/fork-a-repo/) QorusToolkit, commit your changes,
-& [send a pull request](https://help.github.com/articles/using-pull-requests/).
-
-We put together a set of guidelines for contributing to Qore Technologies and it's packages, which are hosted in the [Qore Technologies Organization](https://github.com/qoretechnologies/reqore) on GitHub. The provided guidelines are not rules but recommendations. Use your best judgement, and feel free to propose changes to this document with a pull request.
-
-## We host our open-source on Github
-
-We use github to host our open-source code, to track issues and feature requests, as well as accept pull requests.
-
-> We Use [Github Flow](https://guides.github.com/introduction/flow/index.html) for code contributions
-
-## How to contribute
-
-Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
-
-1. Fork the repo and create your branch from `develop`.
-2. If you've added code that should be tested, add tests.
-3. If you've changed APIs, update the documentation.
-4. Ensure the test suite passes.
-5. Make sure your code lints.
-6. Issue that pull request!
-
-## Any contributions you make will be under the MIT Software License
-
-In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
-
-## Report bugs using Github's issues
-
-We use GitHub issues to track public bugs. Report a bug by opening a new issue on <code>github.com/qoretechnologies/qorus-ui/issues</code> it's that easy!
-
-## Write bug reports with detail, background, and sample code
-
-**Great Bug Reports** tend to have:
-
-- A quick summary and/or background of a bug
-- Steps to reproduce
-  - Be specific!
-  - Give sample code if you can.
-- Expected behavior according to your understanding
-- Current behavior which includes the bug
-- Notes (includes, your reasoning behind the problem or steps you tried to solve the bug)
-
-We _love_ thorough bug reports so that we can act fast on them.
-
-## Use a Consistent Coding Style
-
-> Reference [Facebook's Guidelines](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
-
-- 2 spaces for indentation rather than tabs
-- 100 character line length
-- Run `npm run lint` to conform to our lint rules
-
-## Community
-
-- [GitHub Organization](https://github.com/qoretechnologies) for Official open-source projects
-- [Discord](https://discord.gg/MWUwDKRR) for support, discussion, news and latest release updates
-- [Qore Technologies Website](https://www.qoretechnologies.com)
-
-## License
-
-By contributing, you agree that your contributions will be licensed under its MIT License.
-
-## References
-
-This document was adapted from the open-source contribution guidelines for Reference [Facebook's Guidelines](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
+<div align="center">
+  <br><br><br>
+  <img src="./public/qoreLogo.png" alt="Unstated Logo" width="500">
+  <br><br><br>
+</div>
+
+# Contributing to Qore Technologies
+
+> First off, thanks for taking the time to contribute!
+
+Contributions are always welcome. Before contributing please read the
+[code of conduct](CODE_OF_CONDUCT.md) &
+[search the issue tracker](https://github.com/qoretechnologies/qorus-ui/issues) your issue may have already been discussed or fixed in `master`. To contribute,
+[fork](https://help.github.com/articles/fork-a-repo/) QorusToolkit, commit your changes,
+& [send a pull request](https://help.github.com/articles/using-pull-requests/).
+
+We put together a set of guidelines for contributing to Qore Technologies and it's packages, which are hosted in the [Qore Technologies Organization](https://github.com/qoretechnologies/reqore) on GitHub. The provided guidelines are not rules but recommendations. Use your best judgement, and feel free to propose changes to this document with a pull request.
+
+## We host our open-source on Github
+
+We use github to host our open-source code, to track issues and feature requests, as well as accept pull requests.
+
+> We Use [Github Flow](https://guides.github.com/introduction/flow/index.html) for code contributions
+
+## How to contribute
+
+Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
+
+1. Fork the repo and create your branch from `develop`.
+2. If you've added code that should be tested, add tests.
+3. If you've changed APIs, update the documentation.
+4. Ensure the test suite passes.
+5. Make sure your code lints.
+6. Issue that pull request!
+
+## Any contributions you make will be under the MIT Software License
+
+In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
+
+## Report bugs using Github's issues
+
+We use GitHub issues to track public bugs. Report a bug by opening a new issue on <code>github.com/qoretechnologies/qorus-ui/issues</code> it's that easy!
+
+## Write bug reports with detail, background, and sample code
+
+**Great Bug Reports** tend to have:
+
+- A quick summary and/or background of a bug
+- Steps to reproduce
+  - Be specific!
+  - Give sample code if you can.
+- Expected behavior according to your understanding
+- Current behavior which includes the bug
+- Notes (includes, your reasoning behind the problem or steps you tried to solve the bug)
+
+We _love_ thorough bug reports so that we can act fast on them.
+
+## Use a Consistent Coding Style
+
+> Reference [Facebook's Guidelines](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
+
+- 2 spaces for indentation rather than tabs
+- 100 character line length
+- Run `npm run lint` to conform to our lint rules
+
+## Community
+
+- [GitHub Organization](https://github.com/qoretechnologies) for Official open-source projects
+- [Discord](https://discord.gg/MWUwDKRR) for support, discussion, news and latest release updates
+- [Qore Technologies Website](https://www.qoretechnologies.com)
+
+## License
+
+By contributing, you agree that your contributions will be licensed under its MIT License.
+
+## References
+
+This document was adapted from the open-source contribution guidelines for Reference [Facebook's Guidelines](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)

package/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2023 Qore Technologies, s.r.o.
+Copyright (c) 2020 Qore Technologies, s.r.o.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/README.md

@@ -6,7 +6,7 @@
 
 # @qoretechnologies/reqore
 
-Reqore is a UI library based on React which can be used with any React project to provide customized UI experience.
+Reqore is a UI library based on React which can be used with any React project to provide a customized UI experience.
 
 - Reqore is a comprehensive library of UI components that features our implementation of Qore Technologies design system
 

package/SECURITY.md

@@ -1,5 +1,5 @@
-
-# Reporting and Fixing Security Issues
-
-Please do not open GitHub issues or pull requests - this makes the problem immediately visible to everyone, including malicious actors. Security issues in Qorus Integration Engine UI can be safely reported via email <b>security@qoretechnologies.com</b>
-
+
+# Reporting and Fixing Security Issues
+
+Please do not open GitHub issues or pull requests - this makes the problem immediately visible to everyone, including malicious actors. Security issues in Qorus Integration Engine UI can be safely reported via email <b>security@qoretechnologies.com</b>
+

package/__tests__/collection.test.tsx

@@ -13,7 +13,7 @@ test('Renders basic <Collection /> properly', () => {
   );
 
   expect(document.querySelectorAll('.reqore-collection').length).toBe(1);
-  expect(document.querySelectorAll('.reqore-collection-item').length).toBe(8);
+  expect(document.querySelectorAll('.reqore-collection-item').length).toBe(9);
 });
 
 test('<Collection /> items can be filtered', () => {

package/__tests__/{control_group.text.tsx → control_group.test.tsx}

@@ -9,16 +9,18 @@ import {
   ReqoreUIProvider,
 } from '../src';
 
-test('Renders <Input /> properly', () => {
+test('Renders <ControlGroup /> properly', () => {
   render(
     <ReqoreUIProvider>
       <ReqoreLayoutContent>
         <ReqoreContent>
-          <ReqoreControlGroup minimal>
+          <ReqoreControlGroup>
             <ReqoreInput minimal />
             <ReqoreButton>Hello</ReqoreButton>
             <ReqoreInput disabled />
             <ReqoreInput size='big' />
+            <ReqoreButton>Hello</ReqoreButton>
+            <ReqoreButton>Hello</ReqoreButton>
           </ReqoreControlGroup>
         </ReqoreContent>
       </ReqoreLayoutContent>

package/__tests__/modal.test.tsx

@@ -1,5 +1,5 @@
 import { act, fireEvent, render, screen } from '@testing-library/react';
-import React, { useContext } from 'react';
+import React, { useContext, useState } from 'react';
 import {
   ReqoreButton,
   ReqoreContent,
@@ -7,6 +7,7 @@ import {
   ReqoreLayoutContent,
   ReqoreModal,
   ReqoreUIProvider,
+  useReqore,
 } from '../src';
 
 test('Renders basic <Modal /> properly', () => {
@@ -94,13 +95,52 @@ const ConfirmButton = ({ confirmFn, cancelFn }) => {
   );
 };
 
+const ConfirmButtonFromModal = ({ confirmFn, cancelFn }) => {
+  const { confirmAction } = useReqore();
+  const [isDialogOpen, setIsDialogOpen] = useState(false);
+
+  return (
+    <>
+      <ReqoreButton
+        id='dialog'
+        onClick={() => {
+          setIsDialogOpen(true);
+        }}
+      >
+        Open Dialog
+      </ReqoreButton>
+      {isDialogOpen && (
+        <ReqoreModal
+          isOpen
+          id='confirm'
+          actions={[
+            {
+              label: 'Open Confirm',
+              id: 'open-confirm',
+              onClick: () => {
+                confirmAction({
+                  description: 'Do you really wanna do this?',
+                  onConfirm: () => confirmFn(),
+                  onCancel: () => cancelFn(),
+                });
+              },
+            },
+          ]}
+        >
+          Modal
+        </ReqoreModal>
+      )}
+    </>
+  );
+};
+
 test('Renders confirmation <Modal /> ', () => {
   const confirmFn = jest.fn();
   const cancelFn = jest.fn();
 
   act(() => {
     render(
-      <ReqoreUIProvider>
+      <ReqoreUIProvider options={{ animations: { dialogs: false } }}>
         <ReqoreLayoutContent>
           <ReqoreContent>
             <ConfirmButton confirmFn={confirmFn} cancelFn={cancelFn} />
@@ -130,3 +170,35 @@ test('Renders confirmation <Modal /> ', () => {
 
   expect(cancelFn).toHaveBeenCalledTimes(2);
 });
+
+test('Always renders confirmation <Modal /> properly above a normal modal', () => {
+  const confirmFn = jest.fn();
+  const cancelFn = jest.fn();
+
+  act(() => {
+    render(
+      <ReqoreUIProvider options={{ animations: { dialogs: false } }}>
+        <ReqoreLayoutContent>
+          <ReqoreContent>
+            <ConfirmButtonFromModal confirmFn={confirmFn} cancelFn={cancelFn} />
+          </ReqoreContent>
+        </ReqoreLayoutContent>
+      </ReqoreUIProvider>
+    );
+  });
+
+  fireEvent.click(document.getElementById('dialog')!);
+  expect(document.querySelectorAll('.reqore-modal').length).toBe(1);
+
+  fireEvent.click(screen.getAllByText('Open Confirm')[0]);
+  expect(document.querySelectorAll('.reqore-modal').length).toBe(2);
+  expect(document.querySelectorAll('.reqore-confirmation-modal').length).toBe(1);
+
+  // @ts-ignore
+  const zIndex = document.querySelectorAll('.reqore-modal')[0].style.zIndex;
+  // @ts-ignore
+  const zIndexConfirmation = document.querySelectorAll('.reqore-confirmation-modal')[0].style
+    .zIndex;
+
+  expect(parseInt(zIndexConfirmation)).toBeGreaterThan(parseInt(zIndex));
+});