-
Notifications
You must be signed in to change notification settings - Fork 220
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
Diagnostic path log relative to current working dir #4807
Diagnostic path log relative to current working dir #4807
Conversation
You can try these changes here
|
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.
Will this impact tsv logs in the azure-rest-api-specs repo? Can we try this change there to ensure no issues (unsure if there ia any output processing going on)
The change itself looks good and also useful
I don't think so, @mikeharder is that going to be a problem |
Should be fine for now, since we just show text output to user, we don't parse it. If we wanted to get fancy, we could try to integrate TypeSpecValidation more with GitHub, where errors from |
To improve microsoft#4806 need to cleanup the path resolution close microsoft#2274 ### Before ![image](https://github.com/user-attachments/assets/fe2832ed-b794-4c80-b25a-157aeae3bd07) ### After - From parent folder ![image](https://github.com/user-attachments/assets/e210fd50-e154-4e34-8129-3e6eae8a6018) - From same folder ![image](https://github.com/user-attachments/assets/fb47894b-70df-4857-9a5f-451c9ece5355)
To improve #4806 need to cleanup the path resolution
close #2274
Before
After
From parent folder
From same folder