Skip to content

CC-Widgets Packages setup #237

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 27 commits into from
Nov 13, 2024

Conversation

Shreyas281299
Copy link

@Shreyas281299 Shreyas281299 commented Nov 5, 2024

COMPLETED https://jira-eng-gpk2.cisco.com/jira/browse/SPARK-569253

Changes

Adds basic setup for widget

Functionalities

  • Adds ability to build providers - yarn build:providers
  • Adds ability to build widgets - yarn build:widgets
  • Adds ability to build both at once (providers should be built first) yarn run build
  • Adds ability to build samples, both react based samples and web-component- yarn run build:samples
  • Adds ability to run react samples- yarn samples:serve-react
  • Adds ability to run web-component samples - yarn samples:serve-wc
  • Adds ability to run tests(tests are only setup in widget-cc-station-login)

Testing

  • Built providers
  • Build widgets
  • Build samples
  • Ran samples
  • Ran test for widget-cc-station-login

Copy link

coderabbitai bot commented Nov 5, 2024

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.


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.

@@ -0,0 +1,7 @@
module.exports = {
Copy link
Author

Choose a reason for hiding this comment

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

Created common babelrc which will be imported in each workspace. babelrc is required in each workspace to run jest tests

@@ -43,6 +43,7 @@ reports/
!.env.default
!package.json
!package-lock.json
!tsconfig.json
Copy link
Author

Choose a reason for hiding this comment

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

tsconfig was getting ignore, was causing issues.

@@ -0,0 +1,32 @@
{
Copy link
Author

Choose a reason for hiding this comment

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

The sample app is also a workspace. This will allow us to easily link updated widgets locally.

Copy link
Author

@Shreyas281299 Shreyas281299 Nov 6, 2024

Choose a reason for hiding this comment

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

All the files in this are demo, these will be updated when we add the actual implementation of these widgets.
We can still run and see the basic providers and widgets working and sharing states. Demo added in the desciption

@@ -0,0 +1,15 @@
import React from 'react';
Copy link
Author

Choose a reason for hiding this comment

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

Dummy code for a simple demo.

const HtmlWebpackPlugin = require('html-webpack-plugin');
const {merge} = require('webpack-merge');

const baseConfig = require('../../webpack.config');
Copy link
Author

Choose a reason for hiding this comment

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

Using base webpack config here also

@@ -0,0 +1,14 @@
<!DOCTYPE html>
Copy link
Author

Choose a reason for hiding this comment

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

This is a sample using web-components and NO react. Again dummy code to just show that widgets can be used as web-components

package.json Outdated
Comment on lines 21 to 26
"build": "yarn run build:providers && yarn run build:widgets",
"build:providers": "yarn workspace @webex/widget-provider build:src",
"build:widgets": "yarn workspace @webex/widget-cc-station-login build:src && yarn workspace @webex/widget-cc-user-state build:src",
"samples:build": "yarn workspace @webex/react-samples-app build:src && yarn workspace @webex/web-component-samples-app build:src",
"samples:serve-react": "yarn workspace @webex/react-samples-app serve",
"samples:serve-wc": "yarn workspace @webex/web-component-samples-app serve"
Copy link
Author

Choose a reason for hiding this comment

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

These scripts are similar to js-sdk, so that we dont have to memories a whole new set of commands

Copy link

@arun3528 arun3528 left a comment

Choose a reason for hiding this comment

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

I dont think you have to follow the structure of packages/@webex structure here

yarn workspace can just relay on the folder structure like widgets/cc-station-login etc

the npm package where you are going to publish can be @webex/cc-station-login

The naming looks little messed up i know we did not follow this on the sdk side

Comment on lines 7 to 11
output: {
path: path.resolve(__dirname, 'dist'),
filename: 'index.js', // Set the output filename to index.js
libraryTarget: 'commonjs2',
},
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 move these to global webpack config itself and if there's a need to change, we will override in this file as and when required

Copy link
Author

Choose a reason for hiding this comment

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

moved to global config

@Shreyas281299
Copy link
Author

I dont think you have to follow the structure of packages/@webex structure here

yarn workspace can just relay on the folder structure like widgets/cc-station-login etc

the npm package where you are going to publish can be @webex/cc-station-login

The naming looks little messed up i know we did not follow this on the sdk side

Moved the cc-widgets out of @webex folder.

@arun3528
Copy link

arun3528 commented Nov 12, 2024

Screenshot 2024-11-12 at 10 27 11 AM @Shreyas281299 @mkesavan13 i am still not sure about the folder structure and the naming we have to make it little meaningful

one thing is like naming as its in widgets folder and repo we dont have to add workd widget-cc word all the time could be just cc-stationLogin

you can also change the @webex/widget folder as well if needed

@Shreyas281299
Copy link
Author

Screenshot 2024-11-12 at 10 27 11 AM @Shreyas281299 @mkesavan13 i am still not sure about the folder structure and the naming we have to make it little meaningful

one thing is like naming as its in widgets folder and repo we dont have to add workd widget-cc word all the time could be just cc-stationLogin

you can also change the @webex/widget folder as well if needed

  • Moved widgets inside a contact-center folder
  • renamed all the widgets to 'cc-X'

@mkesavan13 mkesavan13 merged commit 09961ba into webex:feat/cc-widgets Nov 13, 2024
2 checks passed
@sreenara
Copy link
Contributor

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

The release is available on GitHub release

Your semantic-release bot 📦🚀

@sreenara
Copy link
Contributor

🎉 This PR is included in version 1.28.0-eft-pipeline.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@sreenara
Copy link
Contributor

🎉 This PR is included in version 1.27.6-eft.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@sreenara
Copy link
Contributor

🎉 This PR is included in version 1.27.6-eft.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@sreenara
Copy link
Contributor

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

The release is available on GitHub release

Your semantic-release bot 📦🚀

@sreenara
Copy link
Contributor

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

The release is available on GitHub release

Your semantic-release bot 📦🚀

@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 📦🚀

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.

6 participants