Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(native-app): change border radius circle to be full #17155

Merged
merged 2 commits into from
Dec 6, 2024

Conversation

thoreyjona
Copy link
Contributor

@thoreyjona thoreyjona commented Dec 6, 2024

What

Changes in #17042 broke the app since the app has its own theme (not using the same theme as other projects in the monorepo).
I changed the borderRadius.circle to be borderRadius.full.

Checklist:

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • Formatting passes locally with my changes
  • I have rebased against main before asking for a review

Summary by CodeRabbit

  • New Features
    • Updated the border radius terminology for circular elements from circle to full in the theme settings.

This change enhances clarity in design specifications while maintaining all other theme properties.

@thoreyjona thoreyjona requested a review from a team as a code owner December 6, 2024 10:04
Copy link
Contributor

coderabbitai bot commented Dec 6, 2024

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

warning eslint@8.57.0: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning eslint > @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
warning eslint > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning jest > @jest/core > jest-config > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > jest-runtime > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > @jest/reporters > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > @jest/transform > babel-plugin-istanbul > test-exclude > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning storybook > @storybook/cli > puppeteer-core > rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
warning storybook > @storybook/cli > puppeteer-core > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning storybook > @storybook/cli > tempy > del > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning storybook > @storybook/cli > jscodeshift > temp > rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
warning storybook > @storybook/cli > jscodeshift > temp > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning storybook > @storybook/cli > jscodeshift > @babel/plugin-proposal-class-properties@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
warning storybook > @storybook/cli > jscodeshift > @babel/plugin-proposal-optional-chaining@7.21.0: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
warning storybook > @storybook/cli > jscodeshift > @babel/plugin-proposal-nullish-coalescing-operator@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
warning next-auth > querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning next-auth > jose@1.28.2: this version is no longer supported
warning next-auth > @next-auth/typeorm-legacy-adapter > typeorm > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @nx/next > @nx/webpack > stylus > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @nx/next > @nx/webpack > webpack-dev-server > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning @nx/next > @nx/webpack > fork-ts-checker-webpack-plugin > memfs@3.6.0: this will be v4
warning @nx/next > @nx/webpack > webpack-dev-server > webpack-dev-middleware > memfs@3.6.0: this will be v4
warning workspace-aggregator-6bb4a50a-323b-4bb0-a30a-5bd9d76344ee > eslint@8.57.0: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning "@nx/eslint > @nx/js > ts-node@10.9.1" has unmet peer dependency "@types/node@".
warning "@nx/next > @babel/plugin-proposal-decorators@7.25.9" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "styled-components > babel-plugin-styled-components > @babel/plugin-syntax-jsx@7.25.9" has unmet peer dependency "@babel/core@^7.0.0-0".
warning " > styled-components@5.3.6" has unmet peer dependency "react-is@>= 16.8.0".
warning "@nx/react > file-loader@6.2.0" has unmet peer dependency "webpack@^4.0.0 || ^5.0.0".
warning " > ts-node@10.9.2" has unmet peer dependency "@types/node@
".
warning "@vanilla-extract/next-plugin > @vanilla-extract/webpack-plugin@2.3.15" has unmet peer dependency "webpack@^4.30.0 || ^5.20.2".
warning " > next-auth@3.29.10" has incorrect peer dependency "react@^16.13.1 || ^17".
warning " > next-auth@3.29.10" has incorrect peer dependency "react-dom@^16.13.1 || ^17".
warning "next-auth > @next-auth/prisma-legacy-adapter@0.1.2" has unmet peer dependency "@prisma/client@^2.16.1".
warning " > next-usequerystate@1.8.4" has incorrect peer dependency "next@^13.4".
warning "@nx/next > copy-webpack-plugin@10.2.4" has unmet peer dependency "webpack@^5.1.0".

Walkthrough

The changes in this pull request involve a modification to the theme.ts file, specifically renaming the circle property to full within the border.radius section of the theme object. This adjustment affects how circular border radii are defined, while all other properties within the theme object remain unchanged.

Changes

File Change Summary
apps/native/app/src/ui/utils/theme.ts Renamed circle property to full in border.radius of theme object.

Possibly related PRs

  • fix(native-app): fix android crash due to borderRadius set to string value #16009: This PR addresses a crash issue related to the borderRadius property, which is directly connected to the changes made in the main PR regarding the border property in the theme object, specifically the circle to full renaming.
  • fix(native-app): minor fixes #16391: This PR includes minor fixes, one of which involves the removal of a mailto link that previously referenced an email address. While not directly related to the border property, it indicates ongoing adjustments in the UI that may align with the overall theme and styling changes in the main PR.

Suggested labels

automerge

Suggested reviewers

  • snaerseljan

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@thoreyjona thoreyjona added the automerge Merge this PR as soon as all checks pass label Dec 6, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
apps/native/app/src/ui/utils/theme.ts (1)

85-85: Add documentation for the 'full' border radius

Consider adding a comment to clarify that this value creates a circular/pill shape effect when applied to elements.

+      // Creates a circular/pill shape effect
       full: 100,
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3d20608 and 33fc29b.

📒 Files selected for processing (1)
  • apps/native/app/src/ui/utils/theme.ts (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
apps/native/app/src/ui/utils/theme.ts (1)

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."
🔇 Additional comments (1)
apps/native/app/src/ui/utils/theme.ts (1)

85-85: Verify the impact of the border radius change

Let's verify all usages of this border radius value in the native app to ensure the change from 'circle' to 'full' doesn't break existing components.

✅ Verification successful

Let me try a different approach to search for the usage patterns.


Border radius change from 'circle' to 'full' is already in use and consistent

The search results show that theme.border.radius.full is already being used consistently across multiple components in the native app:

  • list-item.tsx
  • notification-card.tsx
  • expandable-card.tsx
  • header.tsx
  • accordion-item.tsx

The change from 'circle' to 'full' appears to be an existing standard, and there are no instances of borderRadius.circle that need updating. The value of '100px' for the 'full' border radius is being referenced correctly in these components.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any usage of borderRadius.circle or borderRadius.full in the native app
echo "Searching for old 'circle' usage that might need updating..."
rg -t tsx -t ts "borderRadius\.(circle|full)" apps/native/

# Look for style definitions that might be affected
echo "Checking for potentially affected style definitions..."
ast-grep --pattern 'style={$_borderRadius$_}' apps/native/

Length of output: 405


Script:

#!/bin/bash
# Search for any usage of borderRadius in the native app
echo "Searching for borderRadius usage..."
rg "borderRadius" apps/native/

# Search for style definitions containing 'circle' or 'full'
echo "Searching for circle/full in styles..."
rg "(circle|full)" apps/native/app/src/ui/

Length of output: 3022

apps/native/app/src/ui/utils/theme.ts Show resolved Hide resolved
Copy link
Member

@eirikurn eirikurn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

codecov bot commented Dec 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 35.73%. Comparing base (a135b0f) to head (78f19b1).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main   #17155   +/-   ##
=======================================
  Coverage   35.73%   35.73%           
=======================================
  Files        6926     6926           
  Lines      147678   147678           
  Branches    42063    42063           
=======================================
+ Hits        52775    52779    +4     
+ Misses      94903    94899    -4     
Flag Coverage Δ
api 3.33% <ø> (ø)
api-domains-auth-admin 48.49% <ø> (ø)
application-system-api 38.78% <ø> (+0.01%) ⬆️
application-template-api-modules 27.81% <ø> (+<0.01%) ⬆️
services-auth-admin-api 52.56% <ø> (ø)
services-auth-delegation-api 58.46% <ø> (ø)
services-auth-ids-api 52.55% <ø> (+0.03%) ⬆️
services-auth-public-api 49.41% <ø> (+<0.01%) ⬆️
services-user-notification 46.63% <ø> (ø)
services-user-profile 56.95% <ø> (-0.07%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 2 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a135b0f...78f19b1. Read the comment docs.

@kodiakhq kodiakhq bot merged commit d1f95c5 into main Dec 6, 2024
56 checks passed
@kodiakhq kodiakhq bot deleted the fix/broken-app-border-radius branch December 6, 2024 11:27
thorhildurt pushed a commit that referenced this pull request Dec 11, 2024
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge this PR as soon as all checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants