Skip to content
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

fix vtests #7048

Merged
merged 1 commit into from Dec 9, 2020
Merged

fix vtests #7048

merged 1 commit into from Dec 9, 2020

Conversation

ecstrema
Copy link
Contributor

@ecstrema ecstrema commented Dec 8, 2020

after 1f0c7ee

export for page number was changed from "-%pageNumber" to " - %pageNumber"

@cbjeukendrup
Copy link
Contributor

Oh oooops... This was my fault, with PR #7019. I changed it, with the idea to make it more convenient for the user, but didn't notice that it would cause problems here. Thanks for fixing it, @Marr11317 !

@ecstrema
Copy link
Contributor Author

ecstrema commented Dec 9, 2020

Oh oooops... This was my fault, with PR #7019. I changed it, with the idea to make it more convenient for the user, but didn't notice that it would cause problems here. Thanks for fixing it, @Marr11317 !

I could have changed it directly in the vtests, but thought that this change might annoy users that are regularly using this export function, since they would then have two different exported files for the same thing. e.g. myscore-1.png and myscore - 1.png

@Jojo-Schmitz
Copy link
Contributor

Spaces in filenames are bad, if created by default

echo " <span>Current</span>" >> $F
echo " <span>Reference</span>" >> $F
echo " <span>After PR</span>" >> $F
echo " <span>Before PR</span>" >> $F
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe just "Before" and "After" are better? or ""change" or, even better "commit" rather than "PR"? Not sure whether vtests are (or should be) used only on PRs.
And they are used again on a subsequent commit to a PR too.

@vpereverzev vpereverzev merged commit 6c0ea0d into musescore:3.x Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants