Merge branch 'master' into rugvip/adopters
This commit is contained in:
Patrik Oldsberg
@@ -0,0 +1,5 @@
|
||||
---
|
||||
'@backstage/plugin-github-pull-requests-board': patch
|
||||
---
|
||||
|
||||
Fix bug on fetching teams repositories where were being filtered by type service unnecessarily
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
'@backstage/backend-common': patch
|
||||
'@backstage/catalog-model': patch
|
||||
'@backstage/core-components': patch
|
||||
'@backstage/plugin-techdocs-react': patch
|
||||
---
|
||||
|
||||
Updated JSDoc to be MDX compatible.
|
||||
@@ -161,6 +161,7 @@ _If you're using Backstage in your organization, please try to add your company
|
||||
| [OVHcloud](https://www.ovhcloud.com/fr/) | [Jean-Philippe Blary](https://github.com/blaryjp), [Arnaud Bauer](mailto:arnaud.bauer@ovhcloud.com), [Flavien Chantelot](https://github.com/Dorn-) | We're providing Backstage to our collaborators to ease their daily jobs, and let them extends it using plugins. |
|
||||
| [Procter & Gamble](https://us.pg.com/) | [Binita Nayak](https://github.com/binitan), [Josh Rose](https://github.com/joshuarose), [RJ Winkler](https://github.com/rjwink) | P&G leverages Backstage to build internal developer portal to ensure developers' happiness. This developer portal shall act as single source of information needed by development teams to seamlessly create, find and maintain their software components/resources/documentation. |
|
||||
| [SANS Institute](https://www.sans.org) | [Christopher Klewin](mailto:cklewin@sans.org) | Developer portal for centralized visibility, reporting, and tooling across multiple organizations. |
|
||||
| [Okay](https://www.okayhq.com/) | [Tomas Barreto](mailto:tomas@okayhq.com)
|
||||
| [Kaluza](https://www.kaluza.com) | [James Condren](mailto:james.condron@kaluza.com) | To provide an automated golden path to developers, with a focus on discovery and documentation |
|
||||
| [LinkedIn](https://linkedin.com) | [Joshua Lawrence](mailto:jlawrence@linkedin.com) | We are building a platform for internal web tools |
|
||||
| [SANS Institute](https://www.sans.org) | [Justin Selleck](mailto:jselleck@sans.org) | SANS uses backstage to track components in github and to facilitate docs near code. |
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
title: GRPC Playground
|
||||
author: Zalopay-OSS
|
||||
authorUrl: https://github.com/zalopay-oss/
|
||||
category: Discovery
|
||||
description: Easily view and test your gRPC API with a GUI Client, inspired from BloomRPC application.
|
||||
documentation: https://github.com/zalopay-oss/backstage-grpc-playground
|
||||
iconUrl: https://raw.githubusercontent.com/zalopay-oss/backstage-grpc-playground/main/images/gprc-logo.png
|
||||
npmPackageName: 'backstage-grpc-playground'
|
||||
@@ -39,8 +39,8 @@ export class FetchUrlReader implements UrlReader {
|
||||
* targets to allow, containing the following fields:
|
||||
*
|
||||
* `host`:
|
||||
* Either full hostnames to match, or subdomain wildcard matchers with a leading `*`.
|
||||
* For example `example.com` and `*.example.com` are valid values, `prod.*.example.com` is not.
|
||||
* Either full hostnames to match, or subdomain wildcard matchers with a leading '*'.
|
||||
* For example 'example.com' and '*.example.com' are valid values, 'prod.*.example.com' is not.
|
||||
*
|
||||
* `paths`:
|
||||
* An optional list of paths which are allowed. If the list is omitted all paths are allowed.
|
||||
|
||||
@@ -24,7 +24,7 @@ import lodash from 'lodash';
|
||||
*/
|
||||
export class CommonValidatorFunctions {
|
||||
/**
|
||||
* Checks that the value is on the form <suffix> or <prefix><separator><suffix>, and validates
|
||||
* Checks that the value is on the form `<suffix>` or `<prefix><separator><suffix>`, and validates
|
||||
* those parts separately.
|
||||
*
|
||||
* @param value - The value to check
|
||||
|
||||
@@ -40,7 +40,7 @@ import { ARROW_MARKER_ID } from './constants';
|
||||
*
|
||||
* @public
|
||||
* @remarks
|
||||
* <NodeData> and <EdgeData> are useful when rendering custom or edge labels
|
||||
* `<NodeData>` and `<EdgeData>` are useful when rendering custom or edge labels
|
||||
*/
|
||||
export interface DependencyGraphProps<NodeData, EdgeData>
|
||||
extends React.SVGProps<SVGSVGElement> {
|
||||
|
||||
@@ -64,7 +64,7 @@ export type ItemCardHeaderProps = Partial<WithStyles<typeof styles>> & {
|
||||
* A simple card header, rendering a default look for "item cards" - cards that
|
||||
* are arranged in a grid for users to select among several options.
|
||||
*
|
||||
* This component expects to be placed within a MUI <CardMedia>.
|
||||
* This component expects to be placed within a MUI `<CardMedia>`.
|
||||
*
|
||||
* Styles for the header can be overridden using the `classes` prop, e.g.:
|
||||
*
|
||||
|
||||
@@ -27,7 +27,6 @@ export function useUserRepositories() {
|
||||
const entitiesList = await catalogApi.getEntities({
|
||||
filter: {
|
||||
kind: 'Component',
|
||||
'spec.type': 'service',
|
||||
'spec.owner': teamEntity?.metadata?.name,
|
||||
},
|
||||
});
|
||||
|
||||
@@ -30,7 +30,7 @@ import { TechDocsAddonLocations, TechDocsAddonOptions } from './types';
|
||||
export const TECHDOCS_ADDONS_KEY = 'techdocs.addons.addon.v1';
|
||||
|
||||
/**
|
||||
* Marks the <TechDocsAddons> registry component.
|
||||
* Marks the `<TechDocsAddons>` registry component.
|
||||
* @public
|
||||
*/
|
||||
export const TECHDOCS_ADDONS_WRAPPER_KEY = 'techdocs.addons.wrapper.v1';
|
||||
|
||||
Reference in New Issue
Block a user