Warn to omit source in custom profile declaration #191
Conversation
|
Docs Build status updates of commit d70f135: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
|
Docs Build status updates of commit 40de7e1: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
| @@ -61,6 +61,9 @@ This stores the name of the profile generator that originated the profile. _Ther | |||
|
|
|||
| **Accepts:** String | |||
|
|
|||
| > [!NOTE] | |||
| > This field should be omitted when declaring custom profile. | |||
There was a problem hiding this comment.
| > This field should be omitted when declaring custom profile. | |
| > This field should be omitted when declaring a custom profile. It is used by Terminal to connect automatically generated profiles to your settings file. |
What do you think?
|
Docs Build status updates of commit 6d32098: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
|
Thanks! |
If the source field specified for custom profile we fail silently.
Let's start with documenting that this field is not expected in custom profile.
See microsoft/terminal#8333.