-
Notifications
You must be signed in to change notification settings - Fork 495
Cleanup tests #7652
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
Cleanup tests #7652
Conversation
@liviuconcioiu the double quotes around the version numbers had been added on purpose at some point. If I remember correctly some of the forks had problems with parsing the yml files otherwise, as the built in yml parser couldn't parse it without. |
So what do you suggest to do in this case? Should I add double quotes to all versions? Right now there's a mix and I want to fix this. Also see @sanchezzzhak comment here #7636 (comment) |
the comment applies to the yaml parser we are using in php, as it automatically tries to determine the type. |
I use a very strict YAML parser in nodejs -
user_agent: Android 12.0
os:
name: Android
version: 12.0 nodejs parse result: {
user_agent: "Android 12.0",
os: {
name: "Android",
version: 12 // Number type
}
} php parse result: [
"user_agent" => "Android 12.0",
"os" => [
"name": "Android",
"version": "12.0"
]
] the current fixtures are all fixed and at the moment I am satisfied, as they do not give errors in the tests total: |
This PR will do exactly this, so all tests are similar in formatting. |
Remove double quotes from version if isn't a float and replaces single quotes with double quotes, especially in podcasting.yml.