Remove default exports in react components that display content

[gidich]

---

For more details, open the Copilot Workspace session.

Summary by Sourcery

Remove default exports from React components and replace them with named exports to enhance code consistency and maintainability.

Enhancements:

• Convert default exports to named exports in React components to improve consistency and maintainability.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request removes default exports from React components that display content, opting for named exports instead. The changes are primarily focused on modifying export statements in various component files.

Class diagram for updated React components

classDiagram
    class App {
        +App()
    }

    class UserInfoContainer {
        +UserInfoContainer()
    }

    class RolesDetailContainer {
        +RolesDetailContainer(RolesDetailContainerProps props)
    }

    class ServiceTicketsDetailContainer {
        +ServiceTicketsDetailContainer(ServiceTicketsDetailContainerProps props)
    }

Loading

File-Level Changes

Change	Details	Files
Converted default export to named export in the main App component	Changed 'function App()' to 'export function App()' Removed 'export default App;' statement at the end of the file	ui-community/src/App.tsx
Removed trailing semicolons from component export statements	Removed semicolon after the closing curly brace of the component definition	ui-community/src/components/layouts/accounts/components/user-info.container.tsx ui-community/src/components/layouts/admin/components/roles-detail.container.tsx ui-community/src/components/layouts/admin/components/service-tickets-detail.container.tsx

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @gidich - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟡 Review instructions: 1 issue found
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (review_instructions): Missing props interface for App component

Please define an interface named 'AppProps' for the component's props, even if it's currently empty. Refer to '002-ui-tsx-files.md' for more information on prop interfaces.

Review instructions:

Path patterns: ui-*/**/*.tsx

Instructions:

• The exported react component name should match the container name (the file name should be kabob-cased, and the component name should be PascalCased) unless the file name is index.tsx, then the component name should match the parent folder name.
• The component should be a functional component.
• An interface or type should be defined for the component's props, named <ComponentName>Props.
  • the props should refer to data only by the fragment name or graphql input type name
• Any use of the AntDesign Table should leverage TableColumnsType and must specify the type of the data (usually the fragment type)
• Any use of the AntDesign useForm hook must specify the type of the form data (usually the GraphQL input type)
• If any of the above rules are broken, direct the developer to refer to the document file named 002-ui-tsx-files.md
• An interface should be defined for the component's props, named <ComponentName>Props.
  • the props should refer to data only by the fragment name or graphql input type name
• Any use of the AntDesign Table should leverage TableColumnsType and must specify the type of the data (usually the fragment type)
• Any use of the AntDesign useForm hook must specify the type of the form data (usually the GraphQL input type)
• If any of the above rules are broken, direct the developer to refer to the document file named 002-ui-tsx-files.md