chore(Portal): allow links in property table types and correct link font size

[snorrekim]

• Make link in inline-code have same font-size
• Make it possible to use link markdown in types
• Other: create a structure that makes it easy to have different styling for primitive types in the future

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
eufemia	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 4, 2025 11:48am

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[snorrekim]

The idea with the new colors is that any type that isn't a primitive should have a different color. Making them more noticeable.

Primitive types are boolean, number, bigint, string andsymbol as well as any array of them like string[] or Array<number>

Comparison to see what I mean:

edit: removed object from list and updated screenshot

[snorrekim]

And here's an example of how allowing link markdown in types can be useful:

The "Step Item" links to it's documentation further below.

[snorrekim]

object should probably also be purple. Like function it doesn't tell the full story. (and it isn't technically a primitive type)

I updated the screenshot above with object as purple

[langz]

Looks good to me :)

The pull request title, chore(Portal): allow links in types and make primitive types purple doesn't seem to align with a statement in the PR description Make non-primitive types purple. Should primitive or non-primitive types be purple? 🤔
Consider updating either description or title 🙏

In the code, I see const colorPrimitive = 'var(--color-success-green)' so primitive types is green and not purple, right? 💭

[snorrekim]

Looks good to me :)

The pull request title, chore(Portal): allow links in types and make primitive types purple doesn't seem to align with a statement in the PR description Make non-primitive types purple. Should primitive or non-primitive types be purple? 🤔 Consider updating either description or title 🙏

In the code, I see const colorPrimitive = 'var(--color-success-green)' so primitive types is green and not purple, right? 💭

Right, the title is wrong, I'll fix it. Primitive types should be green. I'm also going to add false and true to the list of primitives.

[tujoworker]

I believe the property name plays a much more important role during the process of scanning and consuming the documentation. However, the use of colors can be distracting and take away from effectively focusing on the content.

I think we should evaluate other ways to communicate primitives, if it is important to distinguish them.

[snorrekim]

Changed the primitives color back to green for now to finish the PR. The option is still there for the future.

[tujoworker]

Nice 👏 Thank you for this 🎉

[tujoworker]

🎉 This PR is included in version 10.63.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀