-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add SavedObjectsUtils.getConvertedObjectId function #107767
Add SavedObjectsUtils.getConvertedObjectId function #107767
Conversation
Also change document migrator code to use this function instead of using uuidv5 directly.
```typescript | ||
static getConvertedObjectId(namespace: string | undefined, type: string, id: string): string; | ||
``` | ||
|
||
## Parameters | ||
|
||
| Parameter | Type | Description | | ||
| --- | --- | --- | | ||
| namespace | <code>string | undefined</code> | | | ||
| type | <code>string</code> | | | ||
| id | <code>string</code> | | | ||
|
||
<b>Returns:</b> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder why the doc generator didn't pick up the parameter descriptions or the return description 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple ideas:
- The script doesn't regen the docs if the signature didn't change, so if you add the comments on the params after generating this the first time it may not be populated. You can add the
--docs
CLI arg to force this - I wonder if the
{string}
type descriptors are a problem? I usually don't use these since that info is already in the TS signature itself. Not sure how our doc generator handles these. - It may not matter much, we're about to remove this tooling.
```typescript | ||
static getConvertedObjectId(namespace: string | undefined, type: string, id: string): string; | ||
``` | ||
|
||
## Parameters | ||
|
||
| Parameter | Type | Description | | ||
| --- | --- | --- | | ||
| namespace | <code>string | undefined</code> | | | ||
| type | <code>string</code> | | | ||
| id | <code>string</code> | | | ||
|
||
<b>Returns:</b> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple ideas:
- The script doesn't regen the docs if the signature didn't change, so if you add the comments on the params after generating this the first time it may not be populated. You can add the
--docs
CLI arg to force this - I wonder if the
{string}
type descriptors are a problem? I usually don't use these since that info is already in the TS signature itself. Not sure how our doc generator handles these. - It may not matter much, we're about to remove this tooling.
💚 Build SucceededMetrics [docs]To update your PR or re-run it, just comment with: |
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
Also change document migrator code to use this function instead of using uuidv5 directly.
Resolves #107744