@backstage/plugin-catalog-react 0.6.13-next.0 → 0.6.14

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 CHANGED
@@ -1,5 +1,63 @@
1
1
  # @backstage/plugin-catalog-react
2
2
 
3
+ ## 0.6.14
4
+
5
+ ### Patch Changes
6
+
7
+ - 680e7c7452: Updated `useEntityListProvider` and catalog pickers to respond to external changes to query parameters in the URL, such as two sidebar links that apply different catalog filters.
8
+ - f8633307c4: Added an "inspect" entry in the entity three-dots menu, for lower level catalog
9
+ insights and debugging.
10
+ - 19155e0939: Updated React component type declarations to avoid exporting exotic component types.
11
+ - 7bb1bde7f6: Minor API cleanups
12
+ - Updated dependencies
13
+ - @backstage/catalog-client@0.6.0
14
+ - @backstage/core-components@0.8.8
15
+
16
+ ## 0.6.14-next.0
17
+
18
+ ### Patch Changes
19
+
20
+ - 680e7c7452: Updated `useEntityListProvider` and catalog pickers to respond to external changes to query parameters in the URL, such as two sidebar links that apply different catalog filters.
21
+ - 7bb1bde7f6: Minor API cleanups
22
+ - Updated dependencies
23
+ - @backstage/core-components@0.8.8-next.0
24
+
25
+ ## 0.6.13
26
+
27
+ ### Patch Changes
28
+
29
+ - f7257dff6f: The `<Link />` component now accepts a `noTrack` prop, which prevents the `click` event from being captured by the Analytics API. This can be used if tracking is explicitly not warranted, or in order to use custom link tracking in specific situations.
30
+ - 300f8cdaee: Fix bug: previously the filter would be set to "all" on page load, even if the
31
+ `initiallySelectedFilter` on the `DefaultCatalogPage` was set to something else,
32
+ or a different query parameter was supplied. Now, the prop and query parameters
33
+ control the filter as expected. Additionally, after this change any filters
34
+ which match 0 items will be disabled, and the filter will be reverted to 'all'
35
+ if they're set on page load.
36
+ - 6acc8f7db7: Add caching to the useEntityPermission hook
37
+
38
+ The hook now caches the authorization decision based on the permission + the entity, and returns the cache match value as the default `allowed` value while loading. This helps avoid flicker in UI elements that would be conditionally rendered based on the `allowed` result of this hook.
39
+
40
+ - Updated dependencies
41
+ - @backstage/core-components@0.8.7
42
+
43
+ ## 0.6.13-next.1
44
+
45
+ ### Patch Changes
46
+
47
+ - f7257dff6f: The `<Link />` component now accepts a `noTrack` prop, which prevents the `click` event from being captured by the Analytics API. This can be used if tracking is explicitly not warranted, or in order to use custom link tracking in specific situations.
48
+ - 300f8cdaee: Fix bug: previously the filter would be set to "all" on page load, even if the
49
+ `initiallySelectedFilter` on the `DefaultCatalogPage` was set to something else,
50
+ or a different query parameter was supplied. Now, the prop and query parameters
51
+ control the filter as expected. Additionally, after this change any filters
52
+ which match 0 items will be disabled, and the filter will be reverted to 'all'
53
+ if they're set on page load.
54
+ - 6acc8f7db7: Add caching to the useEntityPermission hook
55
+
56
+ The hook now caches the authorization decision based on the permission + the entity, and returns the cache match value as the default `allowed` value while loading. This helps avoid flicker in UI elements that would be conditionally rendered based on the `allowed` result of this hook.
57
+
58
+ - Updated dependencies
59
+ - @backstage/core-components@0.8.7-next.1
60
+
3
61
  ## 0.6.13-next.0
4
62
 
5
63
  ### Patch Changes