Closed Dahie closed 4 years ago
Hi @spilth. maybe this also slipped through the notifications. What are your thoughts here? :)
Hey @Dahie. The stripping is intentional but I don't remember my reasoning behind it. I suspect it has something to do with how I'm displaying things in HTML, but I'm not entirely certain.
If you remove the stripping behavior, does the test suite still pass?
If I make the test above pass, there are 3-4 additional scenarios that will need adjustment in their expectations. For code, see https://github.com/SongProOrg/songpro-ruby/pull/3
@Dahie I'm gonna need to spend some time making this change locally and seeing if affects my other project that relies on this Gem - https://github.com/spilth/mss.nyc
Hey @Dahie. I pulled in your branch, installed the gem locally and tried my site with it and all seems to be well. So I'm gonna merge this in. If there ends up being a problem we can always revert the change.
I'm also gonna update the Ruby version, update any dependencies that need it and push out a new version.
Fixed by @Dahie in #3 and released as 0.1.7: https://rubygems.org/gems/song_pro/versions/0.1.7
Hi,
I don't know if the following is an issue or a conscious decision. Let's assume the following rspec test:
This will fail, because the expectation
expect(song.sections[0].lines[0].parts[1].lyric).to eq 'bout a '
actually returns'bout a'
with stripped whitespaces at the end. Is this intentional?In the software I'm writing at the moment, it does make a difference if a chord is within a word or before a word. With this behaviour, the example is compacted to:
'It's about aboy'