refactor: use isFontStyle, isFontWeight in title setters

[Sachinn-64]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown status: na
• task: lint_package_json status: na
• task: lint_repl_help status: na
• task: lint_javascript_src status: passed
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: na
• task: lint_javascript_tests status: na
• task: lint_javascript_benchmarks status: na
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: na
• task: lint_c_examples status: na
• task: lint_c_benchmarks status: na
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: passed
• task: lint_typescript_tests status: na
• task: lint_license_headers status: passed ---

Resolves None.

Description

What is the purpose of this pull request?

This pull request:

• refactor: use isFontStyle, isFontWeight in title setters

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• None

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

{{TODO: add disclosure if applicable}}

---

@stdlib-js/reviewers

[kgryte]

@Sachinn-64 Looks like you also need to address the failing test. See the CI logs above.

[kgryte]

As commented, we still need to support undefined, the support of which is intentional. Only required configuration properties cannot be "unset". That is why some properties do not include undefined in the set of allowed values, but most do.

[kgryte]

Also, this https://github.com/stdlib-js/stdlib/pull/11934/changes should consolidated into this PR. There is no need to only make changes in this PR and then update the tests separately in another PR. Otherwise, we just merge something which then triggers test failures.

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
plot/vega/title/ctor	$\color{red}4946/4950$ $\color{green}+99.92%$	$\color{red}307/309$ $\color{green}+99.35%$	$\color{green}61/61$ $\color{green}+100.00%$	$\color{red}4946/4950$ $\color{green}+99.92%$

The above coverage report was generated for the changes in this PR.

[kgryte]

LGTM