@backstage/core-components 0.6.0 → 0.7.2
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/CHANGELOG.md +81 -0
- package/dist/index.d.ts +353 -64
- package/dist/index.esm.js +149 -58
- package/dist/index.esm.js.map +1 -1
- package/package.json +17 -17
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,86 @@
|
|
|
1
1
|
# @backstage/core-components
|
|
2
2
|
|
|
3
|
+
## 0.7.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- afd5c82ce1: Updates the d3 dependencies
|
|
8
|
+
- c6c2942daa: Deprecated `DismissbleBannerClassKey` and fixed the typo to make `DismissableBannerClassKey`
|
|
9
|
+
- Updated dependencies
|
|
10
|
+
- @backstage/config@0.1.11
|
|
11
|
+
- @backstage/theme@0.2.12
|
|
12
|
+
- @backstage/errors@0.1.4
|
|
13
|
+
- @backstage/core-plugin-api@0.1.12
|
|
14
|
+
|
|
15
|
+
## 0.7.1
|
|
16
|
+
|
|
17
|
+
### Patch Changes
|
|
18
|
+
|
|
19
|
+
- e535ea766a: Switched to relying on the built-in support for async loading in `react-syntax-highlighter`. This should provide further improvements to async rendering and lazy loading, and avoid test flakiness that was happening because of the significant number or resources being loaded in lazily all at once.
|
|
20
|
+
- 2023a9683f: Fixed invalid wrap in DismissableBanner component
|
|
21
|
+
- 36e67d2f24: Internal updates to apply more strict checks to throw errors.
|
|
22
|
+
- Updated dependencies
|
|
23
|
+
- @backstage/errors@0.1.3
|
|
24
|
+
- @backstage/core-plugin-api@0.1.11
|
|
25
|
+
|
|
26
|
+
## 0.7.0
|
|
27
|
+
|
|
28
|
+
### Minor Changes
|
|
29
|
+
|
|
30
|
+
- 5c42360577: Add documentation and more type safety around DependencyGraph
|
|
31
|
+
- a20cbf00d2: The syntax highlighting library used by the `CodeSnippet` component is now lazy loaded. This most likely has no effect on existing code, but may break tests as the content of the `CodeSnippet` is now rendered asynchronously.
|
|
32
|
+
|
|
33
|
+
### Patch Changes
|
|
34
|
+
|
|
35
|
+
- 75bc878221: Internal refactor to avoid importing all of `@material-ui/core`.
|
|
36
|
+
- 6ec56d5a57: update the null check to use the optional chaining operator in case of non-null assertion operator is not working in function extractInitials(values: string)
|
|
37
|
+
- 81c2a1af86: Resolve a warning in `<Button>` related to not using `React.forwardRef`.
|
|
38
|
+
- 53470ada54: Fix search in Firefox. When the search was performed by pressing enter, the query parameter was first set but then reverted back.
|
|
39
|
+
- b488d8b69f: Change the Table search field placeholder to "Filter" and change icon accordingly
|
|
40
|
+
|
|
41
|
+
We had feedback that users expected the catalog table search field to have more sophisticated behaviour
|
|
42
|
+
than simple filtering. This change sets the search field placeholder to read "Filter"
|
|
43
|
+
to avoid confusion with the search feature. The icon is updated to match. This change is applied
|
|
44
|
+
generally in core-components so this change is made consistently across the app given the search
|
|
45
|
+
field is present on all pages via the sidebar.
|
|
46
|
+
|
|
47
|
+
- 2435d7a49b: Deprecated HomepageTimer in favor of HeaderWorldClock which is found in the [home plugin](https://github.com/backstage/backstage/tree/master/plugins/home)
|
|
48
|
+
- Updated dependencies
|
|
49
|
+
- @backstage/theme@0.2.11
|
|
50
|
+
|
|
51
|
+
## 0.6.1
|
|
52
|
+
|
|
53
|
+
### Patch Changes
|
|
54
|
+
|
|
55
|
+
- f139fed1ac: The `<Link />` component now automatically instruments all link clicks using
|
|
56
|
+
the new Analytics API. Each click triggers a `click` event, containing the
|
|
57
|
+
text of the link the user clicked on, as well as the location to which the user
|
|
58
|
+
clicked. In addition, these events inherit plugin/extension-level metadata,
|
|
59
|
+
allowing clicks to be attributed to the plugin/extension/route containing the
|
|
60
|
+
link:
|
|
61
|
+
|
|
62
|
+
```json
|
|
63
|
+
{
|
|
64
|
+
"action": "click",
|
|
65
|
+
"subject": "Text content of the link that was clicked",
|
|
66
|
+
"attributes": {
|
|
67
|
+
"to": "/value/of-the/to-prop/passed-to-the-link"
|
|
68
|
+
},
|
|
69
|
+
"context": {
|
|
70
|
+
"extension": "ExtensionInWhichTheLinkWasClicked",
|
|
71
|
+
"pluginId": "plugin-in-which-link-was-clicked",
|
|
72
|
+
"routeRef": "route-ref-in-which-the-link-was-clicked"
|
|
73
|
+
}
|
|
74
|
+
}
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
- 666e1f478e: Provide a clearer error message when a authentication provider used by the `SignInPage` has not been configured to support sign-in.
|
|
78
|
+
- 63d426bfeb: Wrap up the `Link` component in a component to reset the color so that we can actually see the button text
|
|
79
|
+
- ca0559444c: Avoid usage of `.to*Case()`, preferring `.toLocale*Case('en-US')` instead.
|
|
80
|
+
- 162e1eee65: SignInPage: move the initial invocation of `login` away from the render method
|
|
81
|
+
- Updated dependencies
|
|
82
|
+
- @backstage/core-plugin-api@0.1.10
|
|
83
|
+
|
|
3
84
|
## 0.6.0
|
|
4
85
|
|
|
5
86
|
### Minor Changes
|