Feature ideas

If I create an enum with a default value (pic 1) then I expect the default value to be populated and visible in entity pages. However it's blank (pic 2). I've tried re-ingesting entities but there's no change.

Specifically to be able to change out-of-the-box tabs such as "Overview" and "Related Entities"

Could you please amend the UI to include a pop-up dialog box that displays the entire string passed to the entity property on the catalog overview page? The team is concerned about not being able to see the complete statement without copying and pasting it elsewhere to understand the full string. Here's an example snippet where the issue occurs (highlighted: Justification): "This will allow us to access the VM from local desktop and VDI, Citrix etc for..." Or make fields like description support longer strings.

It would be nice to embed the markdown from an entities markdown property in a markdown widget. This would be very helpful on the new Entity Overview page.

It’d be nice if we could upload an asset rather than needing to host the logo ourselves.

To allow customers to upload larger Swagger specifications directly into their entities, enhancing API catalog functionality

Currently, the Swagger UI component is only able to authenticate directly using a token added to the request. In scenarios where the spec uses more complicated authentication (Oauth or similar mechanic with a redirect), the UI is not able to authenticate properly. Adding support for that would allow integrations with more complex specs.

Currently, relative links in README.md files imported from GitHub into Port assume Port's base URL, leading to 404 errors. It would be great if Port could support relative links by correctly resolving them based on the GitHub repository's base URL. This enhancement would improve the user experience and ensure seamless navigation of linked resources.

When attempting to explore the related entities tabs from the entity view page, I find myself scrolling a lot, from side to side. Then I often have a very small table by default for each tab, which I then need to scroll vertically

Right now choosing an Object/Json for a blueprint property is less than ideal because it literally displays as json to the user. However, this is not a great experience for the end user because Json is not nice to look at and some users might not understand it. Current implementation is shown in the picture with the red arrow below. My suggestion is to create a better method of displaying object/json inputs to the user as maybe a popup if they click into the object. Such as the below image about user details. Maybe some nicer method of displaying key/value pairs when you click into the object on the entity screen.