Figure.text: Migrate the fill/pen parameters to the new alias system

[seisman]

Just regular migration.

[Copilot]

Pull request overview

Migrates Figure.text/text_ handling of the GMT -G (fill) and -W (pen) options from the legacy @use_alias mechanism to the newer AliasSystem-based alias handling.

Changes:

• Removed G="fill" and W="pen" from the @use_alias decorator and introduced explicit fill/pen keyword parameters.
• Added fill/pen into the AliasSystem construction so they are emitted as -G/-W.
• Tightened type annotations for angle and font, and added an inline type: ignore for a mixed-type list used in validation.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[yvonnefroehlich]

I am wondering about the context of the type bool for angle and font. Why was there a change from None to False? And I am wondering if this causes the newly occuring warning by the Figure.text method, e.g., https://www.pygmt.org/dev/tutorials/basics/text.html:

text [WARNING]: Length <unit> e not supported - revert to default unit [point]
text [WARNING]: Fals not a valid number and may not be decoded properly.
text [WARNING]: Representation of font size not recognized. Using default.

[seisman]

I am wondering about the context of the type bool for angle and font. Why was there a change from None to False?

In Figure.text, angle=True, font=True means the input file contains columns for angle and font, so angle/font can accept bools.

The issue is that when changing the default from None to False, I didn't update the checking of these parameters. #4577 should fix it.

[yvonnefroehlich]

In Figure.text, angle=True, font=True means the input file contains columns for angle and font, so angle/font can accept bools.

Ah, OK. Thanks!