fix: don’t render o-booking__classes if there is no content

[therobrob]

don’t render o-booking__classes if there is no content

Resolves #546

[github-actions]

Hi there! 👋

Thank you for your contribution to the FIP Guide! 🚀
We appreciate your effort in making rail staff travel information more accessible. 🚄

Checklist before merging:

• Added a description to the Pull Request
• Checked the License of new pictures (non-commercial use without attribution)
• Modified content in English
• Modified content in German
• Modified content in French

[netlify]

✅ Deploy Preview for fipguide ready!

Name	Link
🔨 Latest commit	f826435
🔍 Latest deploy log	https://app.netlify.com/projects/fipguide/deploys/696fb9244e8bb800087bb25b
😎 Deploy Preview	https://deploy-preview-598--fipguide.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[MoritzWeber0]

The div is no longer rendered, so that's good, but the free space doesn't seem to be used by the o-booking__meta div, so the text still wraps.

[therobrob]

The div is no longer rendered, so that's good, but the free space doesn't seem to be used by the o-booking__meta div, so the text still wraps.

That’s absolutely intended, see #546 (comment) :)

[therobrob]

@MoritzWeber0 do you wanna merge #615 into this one before merging it? 🤔

[MoritzWeber0]

@MoritzWeber0 do you wanna merge #615 into this one before merging it? 🤔

No, I just had to wait for the pipeline to be green :)

[therobrob]

@MoritzWeber0 do you wanna merge #615 into this one before merging it? 🤔

No, I just had to wait for the pipeline to be green :)

Mhm I don’t get it.. the base branch of #615 was this PR, now we have merge conflicts. But do it your way, it’s fine for me in both ways :D

[MoritzWeber0]

@MoritzWeber0 do you wanna merge #615 into this one before merging it? 🤔

No, I just had to wait for the pipeline to be green :)

Mhm I don’t get it.. the base branch of #615 was this PR, now we have merge conflicts. But do it your way, it’s fine for me in both ways :D

Ahh, yeah, that's because of the squashed commits. But they're easy to resolve with an interactive rebase. I'll take care of it.