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

Add a new tag for line breaks (<br>) #687

Merged
merged 2 commits into from Feb 21, 2022

Conversation

Joo200
Copy link
Contributor

@Joo200 Joo200 commented Feb 20, 2022

Previous problem is here #686 :

Sometimes it's not possible or a bad idea to use \n for a line break. Maybe your message storage doesn't support that (or you'd have to escape it there).

With this PR I want to add a <br> tag as alternative to \n. It'll replace <br> with the Component for a new line.

Copy link
Member

@MiniDigger MiniDigger left a comment

Choose a reason for hiding this comment

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

(needs docs PR)

Copy link
Member

@kezz kezz left a comment

Choose a reason for hiding this comment

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

I think a <newline> alias would be nice as well.

@Joo200
Copy link
Contributor Author

Joo200 commented Feb 20, 2022

I think a <newline> alias would be nice as well.

Not sure about a new alias like that. <br> is already well known by html. Imo too many tags are confusing and using <br> here should be totally fine.

@kezz
Copy link
Member

kezz commented Feb 20, 2022

The majority of MiniMessage users will not be familiar with HTML. I do not see how adding a clearer tag would cause any more confusion.

@zml2008
Copy link
Member

zml2008 commented Feb 20, 2022

I think <newline> would be good as an alias -- there's really no harm in having both options around.

Copy link
Member

@kezz kezz left a comment

Choose a reason for hiding this comment

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

Final nitpicks! After this it's good to go :)

Copy link
Member

@kezz kezz left a comment

Choose a reason for hiding this comment

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

Awesome, thank you for the PR and thanks for being so receptive and understanding of all my nitpicky comments! <3

This was referenced Feb 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants