@orchestrator-ui/orchestrator-ui-components 0.1.1 → 0.2.0

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.
@@ -0,0 +1,11 @@
1
+ $ tsup src/index.ts --format esm --dts
2
+ CLI Building entry: src/index.ts
3
+ CLI Using tsconfig: tsconfig.json
4
+ CLI tsup v7.1.0
5
+ CLI Target: node16
6
+ ESM Build start
7
+ ESM dist\index.js 111.65 KB
8
+ ESM ⚡️ Build success in 90ms
9
+ DTS Build start
10
+ DTS ⚡️ Build success in 3670ms
11
+ DTS dist\index.d.ts 24.53 KB
@@ -0,0 +1,15 @@
1
+ $ eslint "src/**/*.ts*"
2
+
3
+ C:\development\surf\orchestrator-ui\packages\orchestrator-ui-components\src\components\OrchestratorPageTemplate\OrchestratorPageHeader\OrchestratorPageHeader.stories.tsx
4
+ 17:17 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
5
+
6
+ C:\development\surf\orchestrator-ui\packages\orchestrator-ui-components\src\components\OrchestratorPageTemplate\OrchestratorPageTemplate\OrchestratorPageTemplate.stories.tsx
7
+ 17:17 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
8
+
9
+ C:\development\surf\orchestrator-ui\packages\orchestrator-ui-components\src\components\Table\DataGridTable\DataGridTable.tsx
10
+ 103:28 warning 'props' is defined but never used @typescript-eslint/no-unused-vars
11
+
12
+ ✖ 3 problems (0 errors, 3 warnings)
13
+
14
+ (node:11940) [DEP0128] DeprecationWarning: Invalid 'main' field in 'C:\development\surf\orchestrator-ui\node_modules\@orchestrator-ui\eslint-config-custom\package.json' of './dist/index.js'. Please either fix that or report it to the module author
15
+ (Use `node --trace-deprecation ...` to show where the warning was created)
@@ -0,0 +1,19 @@
1
+ yarn run v1.22.19
2
+ $ jest
3
+ PASS Orchestrator UI Components Tests src/utils/getTypedFieldFromObject.spec.ts
4
+ PASS Orchestrator UI Components Tests src/components/Table/DataGridTable/dataGridColumns.spec.ts
5
+ PASS Orchestrator UI Components Tests src/utils/uuid.spec.ts
6
+ PASS Orchestrator UI Components Tests src/utils/string.spec.ts
7
+ PASS Orchestrator UI Components Tests src/components/Table/utils/tableConfigPersistence.spec.ts
8
+ PASS Orchestrator UI Components Tests src/components/Table/utils/columns.spec.ts
9
+ PASS Orchestrator UI Components Tests src/utils/getTokenName.spec.ts
10
+ PASS Orchestrator UI Components Tests src/components/Table/utils/tableUtils.spec.ts
11
+ PASS Orchestrator UI Components Tests src/utils/date.spec.ts
12
+ PASS Orchestrator UI Components Tests src/components/SubscriptionsTabs/getSubscriptionsTabTypeFromString.spec.ts
13
+
14
+ Test Suites: 10 passed, 10 total
15
+ Tests: 50 passed, 50 total
16
+ Snapshots: 0 total
17
+ Time: 4.16 s
18
+ Ran all test suites.
19
+ Done in 5.13s.
@@ -0,0 +1 @@
1
+ $ tsc --noEmit
package/CHANGELOG.md CHANGED
@@ -1,5 +1,17 @@
1
1
  # @orchestrator-ui/orchestrator-ui-components
2
2
 
3
+ ## 0.2.0
4
+
5
+ ### Minor Changes
6
+
7
+ - 6c4cb21: Added translation setup and next-inl configuration. Translation strings are now available when using the useTranslations hook. For more on how to add translations refer to apps/wfo-ui/translations/README.md
8
+
9
+ ## 0.1.2
10
+
11
+ ### Patch Changes
12
+
13
+ - 0cef169: Splitted WFO in separate packages
14
+
3
15
  ## 0.1.1
4
16
 
5
17
  ### Patch Changes