Update --pos tag behavior for single-value input#890
Update --pos tag behavior for single-value input#890KavishaHaswani wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
## Summary of the Pull Request Updated the behavior of the `--pos` command-line argument in documentation. ## References and Relevant Issues Related to #4247 ## Detailed Description of the Pull Request / Additional comments - A single value like `--pos 500` now sets both `x` and `y` to `500`. - A trailing comma (e.g., `--pos 500,`) sets only `x`, using the default for `y`.
|
Learn Build status updates of commit 663248d: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Note: This docs PR is related to the main code PR (microsoft/terminal#19409). The main code changes are pending review, so this PR depends on that one. |
## Summary of the Pull Request Fixes #4247. Improves consistency in -pos tag parsing by supporting single-value input for both axes. ## References and Relevant Issues #4247 ## Detailed Description of the Pull Request / Additional comments The change aligns -pos behavior with padding-style logic. Existing comma-separated behavior remains unchanged. - A single value like "number" now sets both x and y positions to that value — similar to how padding behaves. - A value like "number," (with a trailing comma) continues to set only x, leaving y unchanged. ## Validation Steps Performed - Ran all unit and integration tests - Added unit test to verify single-value and comma-separated inputs ## PR Checklist - [x] Closes #4247 - [x] Tests added/passed - [x] Documentation updated MicrosoftDocs/terminal#890 --------- Co-authored-by: Carlos Zamora <cazamor@microsoft.com>
|
Learn Build status updates of commit 663248d: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 663248d: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
Summary of the Pull Request
Updated the behavior of the
--poscommand-line argument in documentation.References and Relevant Issues
Related to #4247
Detailed Description of the Pull Request / Additional comments
--pos 500now sets bothxandyto500.--pos 500,) sets onlyx, using the default fory.