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

Replace legacy color codes in flag examples #3520

Merged
merged 1 commit into from
May 16, 2022
Merged

Conversation

SirYwell
Copy link
Member

Description

Replaces two usages of legacy color codes in flag value examples.

Submitter Checklist

  • Make sure you are opening from a topic branch (/feature/fix/docs/ branch (right side)) and not your main branch.
  • Ensure that the pull request title represents the desired changelog entry.
  • I tested my changes and approved their functionality.
  • I ensured my changes do not break other parts of the code
  • I read and followed the contribution guidelines

@SirYwell SirYwell requested a review from a team as a code owner February 26, 2022 20:42
@github-actions github-actions bot added Bugfix This PR fixes a bug Ready for Review labels Feb 26, 2022
Copy link
Collaborator

@NotMyFault NotMyFault left a comment

Choose a reason for hiding this comment

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

Minimessage colors are not escaped in the flag description box

@dordsor21 dordsor21 self-requested a review February 27, 2022 15:52
@SirYwell
Copy link
Member Author

SirYwell commented Mar 3, 2022

Minimessage colors are not escaped in the flag description box

I guess templates are currently resolved too by minimessage, I'm wondering if that's still the case in the latest version. If not, we can probably ignore it for now...

@NotMyFault NotMyFault marked this pull request as draft March 30, 2022 18:00
@SirYwell
Copy link
Member Author

This is indeed fixed in the MM version used in v7. Should we still merge it into v6 or retarget it instead?

@NotMyFault
Copy link
Collaborator

NotMyFault commented May 14, 2022

This is indeed fixed in the MM version used in v7. Should we still merge it into v6 or retarget it instead?

-0.9 from me, we can get it covered in v7, which is fine to me.

@SirYwell SirYwell changed the base branch from v6 to v7 May 14, 2022 19:05
@SirYwell SirYwell force-pushed the fix/v6/legacy-color-codes branch from 88accd3 to a188898 Compare May 14, 2022 19:06
@SirYwell
Copy link
Member Author

Retargeted and rebased (we'll just ignore the misleading branch name)

@SirYwell SirYwell marked this pull request as ready for review May 14, 2022 19:07
@NotMyFault NotMyFault self-requested a review May 15, 2022 10:04
@NotMyFault NotMyFault requested a review from a team May 15, 2022 10:20
@NotMyFault
Copy link
Collaborator

Thanks for your contribution! We will merge your PR within the next ~24 hours, as outlined in our PR review process.

@dordsor21 dordsor21 merged commit 953d57d into v7 May 16, 2022
@dordsor21 dordsor21 deleted the fix/v6/legacy-color-codes branch May 16, 2022 12:28
NotMyFault added a commit that referenced this pull request Mar 6, 2023
* Update MiniMessage to 4.10.1 (#3617)

* chore!: bump MiniMessage to 4.10.1

BREAKING CHANGE: bumping MiniMessage and Adventure removes the adventure Template class and breaks the whole messaging system api wise

* chore: fix minimessage messages, fix circular method reference

* build: Update to Paper 1.18.2 (#3622)

build: Align MM and Adventure version

* Replace legacy color codes in flag examples (#3520)

* chore: Change maven group and artifact ID (#3632)

chore: Change maven group and artifact ID

* v7 is 7.0.0-SNAPSHOT

* build: Update bom

* Chore: General deprecations (#3660)

Address deprecations for removal throughout the plugin

* Address deprecations in queue/generation code (#3658)

* Update to new Spigot generation API (#3659)

* Address deprecations in queue/generation code

* Move to new generation API
 - Currently not working due to lack of biome-setting capability via BiomeProvider for flat worlds

* Any fixes to flat world biome setting will target 1.19

* Ensure compiled is actually set to true in BlockBucket

* Delegate to platformGenerator in deprecated generation method if applicable when using new generation methods (1.19)

* Re-add wrongly removed method

* Handle exceptions using logger

* We can simplify getting relative offset using floormod

* Replace many booleans with EnumSet

* Address comments, remove needless boolean return for populateChunk

* Ensure use of new generation methods only on 1.19 and above

* refactor: simplify timeout logic in uuid pipeline (#3760)

simplify timeout logic

* Fix compile errors

* Revert GAV changes

* Update javadoc links

* Start deployment of v7 snapshots

* Temporarily create javadocs for v7 snapshots

* Temporarily create javadocs for v7 snapshots

* Fixes #3919

* Fix relocation of informative annotations

* Drop HTTP4J (#3916)

* Fixes #3906 by fine-graining the help menu generation localization support

* Clean up merge

* *Actually clean up

* chore: Remove things marked as for removal (#3941)

* chore: Remove things marked as for removal

* Address feedback

Co-authored-by: Alexander Brandes <mc.cache@web.de>

* Resolved conflicts

* Cleanup deprecated methods

* Revert "Cleanup deprecated methods"

This reverts commit 26692d6.

* Record-inize methods (#3976)

* Delete unused HyperverseWorldManager file

* Migrate left over occurrences to enhanced switches (#3979)

* Migrate left-overs to enhanced switches

* More

* Cleanup deprecated methods (#3980)

* Perform code formatting according to editorconfig (#3981)

* Perform code reformatting

* Fix javadoc errors

* Don't format JSON files

---------

Co-authored-by: Pierre Maurice Schwang <mail@pschwang.eu>
Co-authored-by: Hannes Greule <SirYwell@users.noreply.github.com>
Co-authored-by: dordsor21 <dordsor21@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bugfix This PR fixes a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants