-
Notifications
You must be signed in to change notification settings - Fork 40
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
Fixes for Windows compatibility (backpatch to 3.7.x) #387
Conversation
Security InsightsNo security relevant content was detected by automated scans. Action Items
Questions or Comments? Reach out on Slack: #support-infosec. |
join()
from package:path
for Windows compatibility (backpatch to 3.7.x)
|
||
test('configFromRunScriptForDart', () { | ||
expect(paths.configFromRunScriptForDart, | ||
r'../../tool/dart_dev/config.dart'); |
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.
Are the path separators for a relative path really not backslashes in windows? If so, how inconsistent.
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.
Turns out this is a path that will be used as an import in a .dart file. Dart always uses forward slashes regardless of the platform. So, nothing to do here.
QA +1
@Workiva/release-management-p |
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.
+1 from RM
There are several paths that we're using in our executable and in the run script that we generate and we need to construct them with the appropriate APIs from
package:path
to ensure they work when running on Windows. This PR does that.