Git Product home page Git Product logo

engage-ui's Introduction

Engage-UI Build Status

Engage-UI is a React component library designed to help developers and designers creater the delightful web experiences.

Installation:

Note: Yarn is not supported to @types/react conflicts among packages

  1. Install latest version of node & npm: https://nodejs.org/en/download/
  2. npm install typescript tslint -g
  3. If there is previously installed packages follow below procedures else jump on 5th point: a. rd /s /q node_modules b. npm cache clear --force
  4. npm i

Building and Running

npm run build-dev: This will build the source code in development mode. npm run build-release: This will build the source code in production mode. npm run test: This will run all unit tests npm run check: This will run all the checks, including lint, build, unit tests. npm run example: This will the example application in ./example/src for testing purposes.

Additional commands can be found in package.json.

Documentation

npm run docs: This will run the documentation application which documents all the components.

Licenses

Feedback

Create an issue or feature request.

engage-ui's People

Contributors

ankitsaraogi avatar captainwild avatar devanshigandhi avatar dheeraja00 avatar dhruvinpatel78 avatar dimplekundanani avatar emgage-smit avatar farhan-emgage avatar hardiksemgage avatar harsimranb avatar hiirenp avatar hirentariwala avatar kimhjona avatar krunalm avatar maannniii avatar mcmuchenje avatar mkulinski avatar nazeerahmad1996 avatar ranak-m avatar romesh87 avatar sadafadrees avatar sagar-vaghela avatar samvora avatar shyamk9 avatar smartnishant avatar sumeet-jadhav avatar tejashrigajjar avatar volodymyr-code avatar webdevlapani avatar weegrom avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar

Forkers

ranmalr krunalm hiirenp tejashrigajjar sandipmehta devanshigandhi dimplekundanani hardiksemgage ishani-m shyamk9 npavlovic renanpallin csumudu

engage-ui's Issues

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Same Id used twice in Labelled component

engage-ui/src/components/Labelled/Labelled.tsx

Line 122 in 98c5965

<div className={wrapperClassName} id={htmlID} style={componentStyle}>

@Farhan-emgage please look into this. The same id is used on line 101 (

engage-ui/src/components/Labelled/Labelled.tsx

Line 101 in 98c5965

componentId={componentId}
) and line 122 (

engage-ui/src/components/Labelled/Labelled.tsx

Line 122 in 98c5965

<div className={wrapperClassName} id={htmlID} style={componentStyle}>
) as htmlID: string = labelID(componentId); (line 117). This creates an accessibility issue, as assistive tech may never read the label as it has the same id as the component render div.

Id attribute not unique for table row more actions button

engage-ui/src/components/Table/RowAction.tsx

Line 86 in 98c5965

<Button componentId={`${componentId}BtnMoreActions`} theme={theme} componentClass={theme.rowActionButton} disabled={actionInProgress} icon="horizontalDots" onClick={(e: React.FormEvent<HTMLElement>) => this.dropdownToggle(e)} title="More Actions">

@Farhan-emgage can you please look into this. A change made by Roman in c75f2ce results in all more action buttons having the same "BtnMoreActions" id. This creates a potential accessibility issue, as only one of the more actions buttons may be available in assistive technologies.

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://[secure]@github.com/emgage/engage-ui#all-merged.

This can be caused by:

Good luck with your project ✨

Your semantic-release bot 📦🚀

TypeScript #7546

When #7546 is resolved, let's add back declaration to tsconfig: { ... , "declaration": true, "declarationDir": "./lib/@types", ... }

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.