@box/types 0.2.0 → 1.0.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.
- package/README.md +1 -36
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,36 +1 @@
|
|
|
1
|
-
|
|
2
|
-
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
|
|
3
|
-
|
|
4
|
-
- [types](#types)
|
|
5
|
-
- [Running commands](#running-commands)
|
|
6
|
-
- [Available commands](#available-commands)
|
|
7
|
-
- [Ownership](#ownership)
|
|
8
|
-
|
|
9
|
-
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
|
|
10
|
-
|
|
11
|
-
# types
|
|
12
|
-
|
|
13
|
-
This library was generated with [@box/automation](../../automation//README.md). General overview on how to perform tasks on the generated library can be found in [run-tasks](https://nx.dev/core-features/run-tasks) Nx documentation.
|
|
14
|
-
|
|
15
|
-
## Running commands
|
|
16
|
-
|
|
17
|
-
Your terminal should stay in location of root directory of repository, which is `frontend-mono`. That Allows Nx to run action against your project, or multiple project if that is necessary.
|
|
18
|
-
Do not navigate to `packages/group-shared-features/types` to run commands.
|
|
19
|
-
|
|
20
|
-
Commands for the project are run using syntax used by Nx:
|
|
21
|
-
|
|
22
|
-
```
|
|
23
|
-
Syntax: yarn nx <target name> <project name> <option overrides>
|
|
24
|
-
| | |
|
|
25
|
-
Example: yarn nx test products --watch
|
|
26
|
-
```
|
|
27
|
-
|
|
28
|
-
## Available commands
|
|
29
|
-
|
|
30
|
-
All commands used with Nx can be found in `project.json` file within your package.
|
|
31
|
-
|
|
32
|
-
- `nx lint types` - run linter over package files
|
|
33
|
-
|
|
34
|
-
## Ownership
|
|
35
|
-
|
|
36
|
-
Code of the feature belongs to UX Foundry team. Responsibilities of owning team include control over code quality, providing guidelines for changes, and alignment with other teams regarding changes. It would be a good practice to consult which team, owning or requesting, will be responsible for implementing changes to code.
|
|
1
|
+
Box Types for TypeScript!
|