Replace branch with pkg name

[dlabrecq]

Replace branch with pkg name in UI version

Summary by Sourcery

Replace branch-based UI version identifier with package name and simplify UiVersion component usage across projects

Enhancements:

• Update UiVersion component to read KOKU_UI_PKGNAME and KOKU_UI_COMMITHASH environment variables instead of using a branch name and appName prop
• Change hidden div id format in UiVersion to use "pkgname_commithash"
• Configure webpack in koku-ui-hccm and koku-ui-ros to inject KOKU_UI_PKGNAME from package.json name and rename existing env vars
• Remove appName prop and package.json imports from all UiVersion usage sites in applications and wrappers

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR refactors the UI version component to use the package name (from package.json) instead of the Git branch for version identification, updating environment variable definitions in Webpack configs and removing the appName prop across application entry points.

File-Level Changes

Change	Details	Files
Refactor UiVersion component to use new env vars	remove UiVersionProps interface and appName prop introduce process.env.KOKU_UI_PKGNAME and process.env.KOKU_UI_COMMITHASH update component id format to ${pkgname}_${commithash}	libs/ui-lib/src/components/page/uiVersion/uiVersion.tsx
Expose KOKU_UI_PKGNAME in Webpack configs	import name from package.json define process.env.KOKU_UI_COMMITHASH instead of COMMITHASH define process.env.KOKU_UI_PKGNAME instead of BRANCH	apps/koku-ui-hccm/fec.config.js apps/koku-ui-ros/fec.config.js
Remove appName prop usage in application code	delete pkg import in optimizationsWrapper remove appName={pkg.name} from UiVersion invocations render UiVersion without props in hccm and ros apps	apps/koku-ui-ros/src/fed-modules/optimizationsWrapper.tsx apps/koku-ui-hccm/src/app.tsx apps/koku-ui-ros/src/app.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. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the 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 exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

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.

[gemini-code-assist]

Summary of Changes

Hello @dlabrecq, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the way UI version information is generated and displayed across the applications. It introduces a more robust and consistent approach by leveraging standardized environment variables for the package name and commit hash, centralizing the logic within the UiVersion component itself. This change streamlines the versioning process and reduces redundancy in how version details are accessed and presented.

Highlights

• Standardized UI Versioning: The UI versioning mechanism has been updated to use the package name (pkgname) instead of the branch name, along with a standardized environment variable for the commit hash (KOKU_UI_COMMITHASH).
• Centralized Version Logic: The UiVersion component now internally retrieves the package name and commit hash from environment variables, removing the need to pass appName as a prop from parent components.
• Webpack Configuration Updates: Webpack configurations in fec.config.js files for koku-ui-hccm and koku-ui-ros have been modified to define the new KOKU_UI_PKGNAME and KOKU_UI_COMMITHASH environment variables.
• Simplified Component Usage: Components like app.tsx and optimizationsWrapper.tsx no longer import package.json directly or pass the appName prop to UiVersion, simplifying their code.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sourcery-ai]

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

---

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.}

[gemini-code-assist]

Code Review

This pull request successfully refactors the UI versioning mechanism by replacing the branch name with the package name. The UiVersion component is now simpler and self-contained, fetching its data from build-time environment variables. The changes are applied consistently across all relevant files. I have one suggestion to further improve the robustness of the generated HTML id in the UiVersion component by sanitizing the package name. This will ensure compatibility with CSS selectors and testing frameworks without requiring character escaping.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.07%. Comparing base (57b270c) to head (df6862f).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4677   +/-   ##
=======================================
  Coverage   87.07%   87.07%           
=======================================
  Files         480      480           
  Lines        9078     9078           
  Branches     2195     2197    +2     
=======================================
  Hits         7905     7905           
- Misses       1107     1108    +1     
+ Partials       66       65    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.