Skip to content

feat(cc-components): setup and move user state sample ui comp #359

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

Merged
merged 18 commits into from
Jan 31, 2025

Conversation

mkesavan13
Copy link
Contributor

@mkesavan13 mkesavan13 commented Jan 16, 2025

Closes Adhoc

This PR addresses

  • Setting up of CC Components monorepo package
  • This will be used to write the presentational layer going forward

by making the following changes

  • Setup a new package CC components
  • Move User State presentational, its relevant types and tests into the CC Components and make the widget consume UI component from here
  • Toggle in WC and React Samples for User State
  • import the momentum web component lib by James' team

The following tests were done

  • Load the React samples and complete station login to see the User State
    • Change state from supervisor to see if UI reflects
    • Change state from UI itself to see if it reflects in the supervisor page and vice versa
  • Load the WC samples and complete station login to see the User State
    • Change state from supervisor to see if UI reflects
    • Change state from UI itself to see if it reflects in the supervisor page and vice versa
  • Also ran the unit test and updated failing one for the change in class name for elapsedTime
  • Check the dark theme in both WC and React samples

Screenshot & Recording

In the below screenshot, on the left notice that the User State UI has loaded and on the right you can see it came from the new cc-components/src package

Screenshot 2025-01-16 at 9 53 02 AM

In the below recording, it shows how a toggle changes the theme of the user state component. Demo is shown in web component sample app but it works in both React and WC Samples:

Screen.Recording.2025-01-25.at.11.50.30.AM.mov

Pending Items

  • Integrating the momentum lib
  • Setup Dark/Light theme toggle
  • Setup i18n facility

Summary by CodeRabbit

  • New Features

    • Added a new User State component for managing agent status and displaying elapsed time
    • Introduced web component integration for the User State component
  • Refactor

    • Migrated presentational component to a new package structure
    • Updated import paths and dependencies across multiple files
  • Documentation

    • Added TypeScript and Webpack configuration files
    • Created package metadata for the new component library
  • Chores

    • Set up build and test configurations for the new component

Copy link

coderabbitai bot commented Jan 16, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This pull request introduces a new package @webex/cc-components with a focus on user state management for a contact center application. The changes include creating a comprehensive package structure with configuration files like .babelrc.js, tsconfig.json, and webpack.config.js. A new UserStateComponent is developed, which provides a reusable React component for displaying and managing agent states, complete with styling and web component integration. The implementation replaces an existing presentational component and updates related dependencies and imports.

Changes

File Change Summary
.babelrc.js New Babel configuration importing base settings
package.json New package definition for @webex/cc-components with dependencies and scripts
src/components/user-state/user-state.scss New SCSS styles for user state component
src/components/user-state/user-state.tsx New React component for rendering user state
src/index.ts Exports new component and type
src/wc.ts Web component registration for user state
tsconfig.json TypeScript configuration with base extension
webpack.config.js Webpack build configuration

Possibly related PRs

Suggested reviewers

  • Shreyas281299

Poem

🐰 A rabbit's tale of code so bright,
User states dancing with pure delight
Components leap from line to line
Web components now intertwine
A digital warren of pure design! 🌈


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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

@mkesavan13
Copy link
Contributor Author

@coderabbitai review

Copy link

coderabbitai bot commented Jan 16, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link

@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

🧹 Nitpick comments (9)
packages/contact-center/user-state/src/user-state/index.tsx (1)

16-16: Consider explicit prop passing instead of prop spreading.

While spreading props works, explicitly passing props improves maintainability and makes prop dependencies clearer:

-  return <UserStateComponent {...props}/>;
+  return (
+    <UserStateComponent
+      idleCodes={props.idleCodes}
+      setAgentStatus={props.setAgentStatus}
+      isSettingAgentStatus={props.isSettingAgentStatus}
+      errorMessage={props.errorMessage}
+      elapsedTime={props.elapsedTime}
+      currentState={props.currentState}
+    />
+  );
packages/contact-center/cc-components/webpack.config.js (2)

17-17: Fix incorrect comment about output filename.

The comment is incorrect as the filename is actually [name].js, not index.js:

-    filename: '[name].js', // Set the output filename to index.js
+    filename: '[name].js', // Output files will be named wc.js and index.js

15-19: Consider adding source map configuration for better debugging.

For better debugging experience in development, consider adding source map configuration:

  output: {
    path: path.resolve(__dirname, 'dist'),
    filename: '[name].js',
    libraryTarget: 'commonjs2',
+    devtoolModuleFilenameTemplate: 'webpack://[namespace]/[resource-path]?[loaders]'
  },
+  devtool: process.env.NODE_ENV === 'development' ? 'source-map' : false,

Note: Based on the retrieved learning, bundle size optimizations are handled in separate tickets, so we'll skip those suggestions.

packages/contact-center/cc-components/src/components/user-state/user-state.tsx (4)

10-15: Consider extracting formatTime to a shared utility.

The formatTime function is well-implemented but could be useful across other components. Consider moving it to a shared utilities file for better code reuse.

-  const formatTime = (time: number): string => {
-    const hours = Math.floor(time / 3600);
-    const minutes = Math.floor((time % 3600) / 60);
-    const seconds = time % 60;
-    return `${hours.toString().padStart(2, '0')}:${minutes.toString().padStart(2, '0')}:${seconds.toString().padStart(2, '0')}`;
-  };

Create a new file src/utils/time.ts:

export const formatTime = (time: number): string => {
  const hours = Math.floor(time / 3600);
  const minutes = Math.floor((time % 3600) / 60);
  const seconds = time % 60;
  return `${hours.toString().padStart(2, '0')}:${minutes.toString().padStart(2, '0')}:${seconds.toString().padStart(2, '0')}`;
};

23-23: Remove empty div.

This empty div with flex styles doesn't serve any purpose.

-            <div style={{ display: 'flex', flexDirection: 'column', flexGrow: 1 }} />

29-33: Optimize the event handler implementation.

The filter operation inside the onChange handler could be optimized by using find instead of filter, as we only need the first matching item.

-                  const code = idleCodes?.filter(code => code.id === event.target.value)[0];
+                  const code = idleCodes?.find(code => code.id === event.target.value);
                   setAgentStatus(code);

49-49: Move error message styling to SCSS.

For consistency, move the inline error styling to the SCSS file.

-              errorMessage && <div style={{color: 'red'}}>{errorMessage}</div>
+              errorMessage && <div className="error-message">{errorMessage}</div>

Add to user-state.scss:

.error-message {
  color: red;
}
packages/contact-center/cc-components/tests/components/user-state/user-state.tsx (1)

57-60: Enhance test coverage for elapsed time styling.

Consider adding tests for the following scenarios:

  • Verify that elapsed time formatting works with edge cases (0 seconds, large numbers)
  • Test that the disabled state properly prevents user interactions
it('should handle edge cases in elapsed time formatting', () => {
  const { rerender } = render(<UserStatePresentational {...defaultProps} elapsedTime={0} />);
  expect(screen.getByText('00:00:00')).toBeInTheDocument();

  rerender(<UserStatePresentational {...defaultProps} elapsedTime={359999} />);  // 99:59:59
  expect(screen.getByText('99:59:59')).toBeInTheDocument();
});
packages/contact-center/cc-components/package.json (1)

60-61: Address the TODO comment in Jest configuration.

The comment indicates that passWithNoTests can be removed when tests are added. Since tests have been implemented, this configuration can be removed.

-    "//": "We can remove this when we have tests",
-    "passWithNoTests": true,
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1f67485 and 123b4e2.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (12)
  • packages/contact-center/cc-components/.babelrc.js (1 hunks)
  • packages/contact-center/cc-components/package.json (1 hunks)
  • packages/contact-center/cc-components/src/components/user-state/user-state.scss (1 hunks)
  • packages/contact-center/cc-components/src/components/user-state/user-state.tsx (1 hunks)
  • packages/contact-center/cc-components/src/index.ts (1 hunks)
  • packages/contact-center/cc-components/src/wc.ts (1 hunks)
  • packages/contact-center/cc-components/tests/components/user-state/user-state.tsx (2 hunks)
  • packages/contact-center/cc-components/tsconfig.json (1 hunks)
  • packages/contact-center/cc-components/webpack.config.js (1 hunks)
  • packages/contact-center/user-state/package.json (1 hunks)
  • packages/contact-center/user-state/src/user-state/index.tsx (2 hunks)
  • packages/contact-center/user-state/src/user-state/user-state.presentational.tsx (0 hunks)
💤 Files with no reviewable changes (1)
  • packages/contact-center/user-state/src/user-state/user-state.presentational.tsx
✅ Files skipped from review due to trivial changes (3)
  • packages/contact-center/cc-components/.babelrc.js
  • packages/contact-center/cc-components/tsconfig.json
  • packages/contact-center/cc-components/src/components/user-state/user-state.scss
🧰 Additional context used
📓 Learnings (1)
packages/contact-center/cc-components/webpack.config.js (1)
Learnt from: Shreyas281299
PR: webex/widgets#345
File: packages/contact-center/cc-widgets/webpack.config.js:6-12
Timestamp: 2024-12-04T07:40:14.028Z
Learning: In the webex-widgets project, optimizations such as reducing bundle size and improving webpack configurations in files like `packages/contact-center/cc-widgets/webpack.config.js` are handled in separate tickets.
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: setup_test_release
🔇 Additional comments (4)
packages/contact-center/cc-components/src/wc.ts (1)

1-8: Well-implemented web component registration!

Good practices observed:

  • Safe custom element registration with duplicate check
  • Proper naming convention with 'component-' prefix
  • Clean usage of r2wc for React to Web Component conversion
packages/contact-center/cc-components/src/components/user-state/user-state.tsx (1)

1-8: LGTM! Clean imports and proper TypeScript usage.

The component is well-structured with proper type definitions and imports.

packages/contact-center/user-state/package.json (1)

22-22: LGTM! Proper workspace dependency configuration.

The addition of @webex/cc-components as a workspace dependency is correct and aligns with the monorepo structure.

packages/contact-center/cc-components/package.json (1)

41-53: Review polyfill dependencies.

Several browser polyfills are included in devDependencies. Please verify if all of these are necessary for the build process:

  • crypto-browserify
  • os-browserify
  • querystring-es3
  • stream-browserify
  • url
  • util
  • vm-browserify

Consider removing unused polyfills to reduce package size and build complexity.

Copy link
Contributor

@Kesari3008 Kesari3008 left a comment

Choose a reason for hiding this comment

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

  1. Do we plan to implement this for other widgets as well or is this for user state only ?
  2. Please fix the failed UT and merge conflicts

@mkesavan13
Copy link
Contributor Author

Hi @Kesari3008,

  1. Do we plan to implement this for other widgets as well or is this for user state only ?

We are doing it for User State as an example of how this would go. So, for other widgets, anyone who picks the UI work will take care

  1. Please fix the failed UT and merge conflicts

Done. Please check.

package.json Outdated
@@ -17,6 +17,7 @@
"@semantic-release/git": "^10.0.1",
"@semantic-release/github": "^11.0.1",
"@testing-library/react-hooks": "^8.0.1",
"copy-webpack-plugin": "^6.3.1",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Remove this. Not necessary

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

Comment on lines 62 to 66
"@momentum-ui/core": ">=19.16.0",
"@momentum-ui/icons": ">=8.28.5",
"@momentum-ui/tokens": ">=1.7.1",
"@momentum-ui/utils": ">=6.2.15",
"@momentum-ui/web-components": ">=2.16.16"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Add react and react-dom as peer-dependencies

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

const props: IUserState = useUserState({
idleCodes,
agentId,
cc
cc,
currentTheme
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Do not send currentTheme to the hook

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Add todo to investigate if there's a better way to theming

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done both. Added todo in open items jira

@@ -20,6 +20,7 @@ class Store implements IStore {
idleCodes: IdleCode[] = [];
agentId: string = '';
selectedLoginOption: string = '';
currentTheme: string = 'light';
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This should be all caps

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

import {StationLogin, UserState, IncomingTask, TaskList, store} from '@webex/cc-widgets';

function App() {
const [isSdkReady, setIsSdkReady] = useState(false);
const [accessToken, setAccessToken] = useState('');
const [isLoggedIn, setIsLoggedIn] = useState(false);
const themeCheckbox = useRef(null);
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Suggested change
const themeCheckbox = useRef(null);
const themeCheckboxRef = useRef(null);

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done


import './user-state.scss';

const UserStateComponent: React.FunctionComponent<IUserState> = (props) => {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Try adding any return type and see if we still require ts ignore

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is not working. Added Todo to the Open Items Jira

Copy link
Contributor

Choose a reason for hiding this comment

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

We should avoid making the component itself an arrow function. It could be normal named function, would help with error trace.

Copy link
Contributor

@rarajes2 rarajes2 left a comment

Choose a reason for hiding this comment

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

Are we not keeping the conventional file names in react as PascalCase? Also the filename should match the component name.

Comment on lines 8 to 15
const {idleCodes,setAgentStatus,isSettingAgentStatus, errorMessage, elapsedTime, currentState, currentTheme} = props;

const formatTime = (time: number): string => {
const hours = Math.floor(time / 3600);
const minutes = Math.floor((time % 3600) / 60);
const seconds = time % 60;
return `${hours.toString().padStart(2, '0')}:${minutes.toString().padStart(2, '0')}:${seconds.toString().padStart(2, '0')}`;
};
Copy link
Contributor

Choose a reason for hiding this comment

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

This can be a utility function.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

},
"dependencies": {
"@r2wc/react-to-web-component": "2.0.3",
"@webex/cc-store": "workspace:*"
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need this dependency here? The presentational layer should not be directly using the outer states

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes. We need this for a type import. On bundle, the whole cc-store won't come in as the tree-shaking would happen.

}
}

.dark-theme {
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's create a JIRA to investigate how we should implement the theming part. Keeping performance and code readability in mind

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We have this added as part of Open Items Jira: https://jira-eng-gpk2.cisco.com/jira/browse/SPARK-608946


import './user-state.scss';

const UserStateComponent: React.FunctionComponent<IUserState> = (props) => {
Copy link
Contributor

Choose a reason for hiding this comment

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

We should avoid making the component itself an arrow function. It could be normal named function, would help with error trace.

};

return (
<>
Copy link
Contributor

Choose a reason for hiding this comment

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

This seems to be unnecessary. We can remove this fragment

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

.elapsedTime-disabled {
color: #777; /* Darker gray for disabled state */
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

nitpick: Always leave a blank line at the end of the file

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

"@momentum-ui/icons": "8.28.5",
"@momentum-ui/tokens": "1.7.1",
"@momentum-ui/utils": "6.2.15",
"@momentum-ui/web-components": "^2.16.16",
Copy link
Contributor

Choose a reason for hiding this comment

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

We are not consistent with the versioning. Somewhere we are keeping it exact and somewhere we are leaving the room for patches

Copy link
Contributor Author

Choose a reason for hiding this comment

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

For everything else, there's no more development since this is the old repo and only @momentum-ui/web-components is under active development. That is why we allow patching for it.

@mkesavan13
Copy link
Contributor Author

Are we not keeping the conventional file names in react as PascalCase? Also the filename should match the component name.

@rarajes2 - No. Across our repository, you can see that the file names are hyphenated and the folder names are PascalCase. For now, I will match it.

I will try to make another PR to match the PascalCase convention

@mkesavan13
Copy link
Contributor Author

We should avoid making the component itself an arrow function. It could be normal named function, would help with error trace.

@rarajes2 - Again, all of the components are arrow functions at the moment. We can discuss as a team and clean it up in another PR

@Shreyas281299 Shreyas281299 merged commit 16a44d0 into webex:ccwidgets Jan 31, 2025
2 checks passed
@sreenara
Copy link
Contributor

sreenara commented Feb 5, 2025

🎉 This PR is included in version 1.28.0-ccconnectors.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@mkesavan13 mkesavan13 deleted the components-monorepo branch February 5, 2025 12:31
@sreenara
Copy link
Contributor

sreenara commented Feb 6, 2025

🎉 This PR is included in version 1.28.0-ccwidgets.14 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

mkesavan13 pushed a commit to mkesavan13/widgets that referenced this pull request Feb 7, 2025
# [1.28.0-ccconnectors.1](webex/widgets@v1.27.5...v1.28.0-ccconnectors.1) (2025-02-05)

### Bug Fixes

* add material to all components ([webex#376](webex#376)) ([de0ca28](webex@de0ca28))
* **bundling:** fixed the multiple React instance and useRef errors  ([webex#355](webex#355)) ([473cd4f](webex@473cd4f))
* **call-control:** add-call-control-widget ([webex#362](webex#362)) ([a677f5e](webex@a677f5e))
* **cc-station-login:** material design ui ([webex#377](webex#377)) ([aec7034](webex@aec7034))
* **cc-store:** receive webex on init, add store types ([webex#341](webex#341)) ([9648969](webex@9648969))
* **cc-widgets:** ship-all-widgets-together ([webex#345](webex#345)) ([83d5a37](webex@83d5a37))
* cleanup and using mobx-react-lite ([webex#356](webex#356)) ([0b304c4](webex@0b304c4))
* convert npm to yarn ([webex#234](webex#234)) ([432ed3c](webex@432ed3c))
* **release:** add-publish-step-in-tooling ([webex#334](webex#334)) ([ca32235](webex@ca32235))
* rename agent state to user state ([webex#361](webex#361)) ([fe409db](webex@fe409db))
* **samples:** change samples index html hrefs ([webex#367](webex#367)) ([ff126ab](webex@ff126ab))
* **user-state:** receive agent stateChange event ([webex#350](webex#350)) ([21d6ce7](webex@21d6ce7))

### Features

* **cc-components:** setup and move user state sample ui comp ([webex#359](webex#359)) ([16a44d0](webex@16a44d0))
* **cc-store:** add logger from sdk ([webex#354](webex#354)) ([a62494b](webex@a62494b))
* **cc-widgets:** added Agent-Multi-Login-Alert Feature ([webex#364](webex#364)) ([f7d75ca](webex@f7d75ca))
* **release:** add new branch to circleci ([18f7bec](webex@18f7bec))
* **release:** publish pipeline for wxcc widgets ([webex#324](webex#324)) ([864fb52](webex@864fb52))
* taskList and IncomingTask widgets added ([webex#348](webex#348)) ([ce3a619](webex@ce3a619))
* **user-state:** load and change state, client timer ([webex#347](webex#347)) ([f1ccaeb](webex@f1ccaeb))
* **widget-cc-station-login:** Spark 575845 login widget ([webex#239](webex#239)) ([66b8a20](webex@66b8a20))
* **widgets:** added-relogin-logic ([webex#357](webex#357)) ([94dd415](webex@94dd415))
* **widgets:** shifted-timer-to-worker ([webex#352](webex#352)) ([c06fe9c](webex@c06fe9c))
rsarika pushed a commit to rsarika/widgets that referenced this pull request Feb 7, 2025
# [1.28.0-ccwidgets.14](webex/widgets@v1.28.0-ccwidgets.13...v1.28.0-ccwidgets.14) (2025-02-06)

### Bug Fixes

* **cc-components:** replace momentum-ui with momentum-design lib ([webex#378](webex#378)) ([b98d76c](webex@b98d76c))

### Features

* **cc-components:** setup and move user state sample ui comp ([webex#359](webex#359)) ([16a44d0](webex@16a44d0))
* **cc-widgets:** added Agent-Multi-Login-Alert Feature ([webex#364](webex#364)) ([f7d75ca](webex@f7d75ca))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants