@talxis/base-controls 1.2509.1 → 1.2509.2

package/LICENSE.md

@@ -0,0 +1,49 @@
+# TALXIS License
+
+## Definitions
+
+“**Software**” means the source code and all related materials provided under this license.
+
+“**Commercial Use**” means any use of the software for the purpose of generating revenue or economic benefit.
+
+“**Licensor**” is NETWORG, the copyright holder and provider of the Software.
+
+## Non-Commercial Use
+
+The Software may be used free of charge for any non-Commercial Use, whether in open-source or closed-source applications.
+
+## Commercial Use
+
+1. Organizations with an annual revenue below 1,000,000 CZK may use the Software for Commercial Use free of charge, provided that all modifications to the Software remain open-source as specified in Section 4.
+2. For determining the revenue threshold, the total revenue of a group of affiliated entities shall be considered.
+3. Organizations with an annual revenue of 1,000,000 CZK or more must obtain a paid license from Licensor before any Commercial Use.
+
+## Modifications and Redistribution
+
+Any modification of the Software must be made publicly available under this license or a compatible open source license.
+
+Distribution of the Software or modified versions of the Software is permitted only if:
+
+1. this licence remains intact
+2. a clear link to the original source code is provided with a link to the Licensor GitHub repository.
+3. all terms of this license are complied with
+
+## Commercial Closed-Source Use
+
+Using the Software in closed-source Commercial Use (where modifications to the Software are not made publicly available) is permitted only under a separate licensing agreement with Licensor, regardless of the organization's revenue.
+
+## Liability Limitation
+
+INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT, THE SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY KIND OF WARRANTY, EXPRESS OR IMPLIED.  In any case, whether in a contract, tort, or other action, the authors, Licensor or copyright holders will not be held accountable for any claims, damages, or other liabilities resulting from, out of, or connected to the Software or the use or other dealings in the Software.
+
+## Area of Cover
+
+This licence applies worldwide.
+
+## Termination
+
+Any breach of this license's terms immediately terminate your right to use the Software and could lead to legal action.
+
+## Contribution
+
+By contributing to the Software, you agree that your contributions will be licensed under the same terms as this license.

package/README.md

@@ -1,41 +1,4 @@
-# Running locally build package in PCF
-
-1. Run `npm install` inside the root directory.
-1. Run `npm run build`.
-1. Run `pnpm link --global`
-1. Navigate to the PCF root directory
-1. Run `pnpm link --global @talxis/base-controls`
-1. Run `npm start watch`.
-
-If you make any changes in the package and re-build it with `npm run build`, it will automatically re-build the PCF and show your changes.
-
-# Running locally build package in Portal
-
-1. Run `npm install` inside the root directory.
-1. Run `npm run build`.
-1. Run `npm link`.
-1. Navigate to the `Portal.Web.Frontend` directory.
-1. Add the following prop in the `vite.config.mts` file under `defineConfig`:
-
-```typescript
-optimizeDeps: {
-    exclude: ['@talxis/base-controls']
-}
-```
-8. Run `npm install`
-9. Run `npm link @talxis/base-controls`
-10. Run `npm start`
-
-These steps only need to be done once. If you want to see any future changes you made in the package, you need to run `npm run build` in package root directory and Portal will automatically reload with your changes applied.
-
-**Don't forget to revert the `vite.config.mts` file to the original version before pushing any changes to the Portal repo!**
-
-## Troubleshooting
-
-If your PCF/Portal builds, but you get an `Hooks can only be called inside of the body of a function component` error during runtime, you need to link the version of React from your PCF/Portal to the package:
-
-1. Navigate to the root directory.
-2. Run `npm` link `<path-to-react> <path-to-react-dom>`
-
-Easiest way to do this is drag the `react` and `react-dom` folders from your PCF/Portal `node_modules` folder into the terminal window where you write the `npm link` command.
+# @talxis/base-controls
 
+## Developing
+Refer to [Developing](./docs/developing.md) for more information.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@talxis/base-controls",
-  "version": "1.2509.1",
+  "version": "1.2509.2",
   "description": "Set of React components that natively work with Power Apps Component Framework API's",
   "main": "dist/index.js",
   "module": "dist/index.js",