fix(sdk): API page styling issues by paanSinghCoder · Pull Request #1456

fix(sdk): API page styling issues by paanSinghCoder · Pull Request #1456 · raystack/frontier

Summary

fix (SDK): Match API page padding with other pages.
fix (SDK): content overflowing out of the modal if key name doesn't have space. Added word wrap.

Before:

After:

Test Plan

Manual testing completed
Build and type checking passes

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Summary by CodeRabbit

Style
- Improved text wrapping behavior for API key token titles in the details view to better handle long text and prevent overflow.

Walkthrough

This PR updates the API keys service user detail page by adding a CSS class for safer text wrapping on token titles and refactoring the page layout to remove unnecessary centering and wrapper components.

Changes

Cohort / File(s)	Summary
Service User Detail Page Styling & Layout `web/sdk/react/views/api-keys/details/service-user-detail-page.tsx`, `web/sdk/react/views/api-keys/details/service-user.module.css`	Added `.serviceKeyItemTitle` CSS class with word-break properties for safer text wrapping. Applied the new class to token title Text element. Simplified page layout by removing outer centering Flex wrapper and inner styles.content wrapper, replacing with a single Flex container.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

bug

Suggested reviewers

rsbh
rohanchkrabrty
rohilsurana

📝 Coding Plan

Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Pull Request Test Coverage Report for Build 23336677723

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0 changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 40.845%

Totals
Change from base Build 23336666086:	0.0%
Covered Lines:	14381
Relevant Lines:	35209