refactor: render null instead of empty fragment when hideTabs is true (#770)

[Copilot]

Closes #770.

In EntityDetailView, the Tabs prop conditionally rendered an empty fragment when hideTabs is true. Changed to render null instead, following React's standard pattern for conditional rendering.

Changes

• src/views/EntityDetailView/entityDetailView.tsx: Replace <></> with null in Tabs prop ternary

// Before
Tabs={
  hideTabs ? (
    <></>
  ) : (
    <Tabs onTabChange={onTabChange} tabs={tabs} value={tabRoute} />
  )
}

// After  
Tabs={
  hideTabs ? null : (
    <Tabs onTabChange={onTabChange} tabs={tabs} value={tabRoute} />
  )
}

Original prompt

---

This section details on the original issue you should resolve

<issue_title>refactor: render null instead of empty fragment when hideTabs is true</issue_title>
<issue_description>## Summary

In EntityDetailView, when hideTabs is true, the Tabs prop currently renders an empty fragment <></>. This should be changed to render null instead, which is the preferred React pattern for conditionally rendering nothing.

Current Code

Tabs={
  hideTabs ? (
    <></>
  ) : (
    <Tabs onTabChange={onTabChange} tabs={tabs} value={tabRoute} />
  )
}

Proposed Change

Tabs={
  hideTabs ? null : (
    <Tabs onTabChange={onTabChange} tabs={tabs} value={tabRoute} />
  )
}

File Location

src/views/EntityDetailView/entityDetailView.tsx (line 82)

Why

• null is the idiomatic React way to render nothing
• Avoids creating an unnecessary empty fragment node
• Cleaner and more explicit intent</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Render null instead of empty fragment when hideTabs is true #770

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[frano-m]

LGTM @copilot thank you.