You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* The virtual environment can be replaced with another setup locally.
385
385
* Above, the `./requirements.txt` file has [the ADR tool][tools] to install.
386
386
387
+
## Release/publish
388
+
389
+
Publishing this repository's npm packages and creating a corresponding GitHub release with git tag (latest only), all happen on GitHub CI.
390
+
391
+
### Publish next packages
392
+
393
+
A set of `next` package is automatically published to `npm` every time a PR is merged.
394
+
395
+
### Publish latest / release
396
+
397
+
Whenever a new release is desired, including publishing a corresponding set of `latest` package to `npm`, it can be triggered through a PR. The following has to be done:
Then decide if the release shall be a `Major`, `Minor` or `Patch` release and use the corresponding command below to step packages versions, according to the release type. A new release commit will be created:
405
+
406
+
``` bash
407
+
yarn version:major
408
+
# or
409
+
yarn version:minor
410
+
# or
411
+
yarn version:patch
412
+
```
413
+
414
+
Modify the _version tag_ in file `./RELEASE`, to match the new release. Then amend the release commit to include this change:
415
+
416
+
```bash
417
+
<edit ./RELEASES to update tag>
418
+
git add RELEASE && git commit --amend
419
+
```
420
+
421
+
Finally, push the branch and use it to create a PR. When the PR is merged, a GitHub release should be created with auto-generated release notes, as well as a git tag. Then the `publish-latest` CI job should trigger and if everything goes well, publish the new version of the repo's packages to `npm`.
The Trace Viewer react-components package contains views and utilities for visualizing traces and logs via the Trace Server Protocol connected a Trace Server applications. While being initially used within the Theia Trace Viewer extension, its code base is independent to any Theia APIs and hence can be integrated in other web applications.
3
+
The Trace Viewer react-components package contains views and utilities for visualizing traces and logs via the Trace Server Protocol, connected a Trace Server application. While being initially used within the Theia Trace Viewer extension, its code base is independent to any Theia APIs and hence can be integrated in other web applications.
4
4
5
5
## Styling
6
6
7
-
The Trace Viewer react-components package does not define CSS styles for its components, but it provides CSS variables that can be map to custom CSS styles or variables. Any projects that use the package should define its own CSS styles for the components. All the mappable variables have the prefix `--trace-viewer`.
7
+
The Trace Viewer react-components package does not define CSS styles for its components, but it provides CSS variables that can be map to custom CSS styles or variables. Any project that uses the package should define its own CSS styles for the components. All the mappable variables have the prefix `--trace-viewer`.
8
8
9
-
An example (of integration with Theia) that contains all the mappable variables can be found in [here](../../theia-extensions/viewer-prototype/style/trace-viewer.css).
9
+
An example (of integration with Theia) that contains all the mappable variables can be found in [here](https://github.com/eclipse-cdt-cloud/theia-trace-extension/blob/master/theia-extensions/viewer-prototype/style/trace-viewer.css).
0 commit comments