{"id":19977797,"url":"https://github.com/uipath/angular-components","last_synced_at":"2025-06-16T15:07:41.617Z","repository":{"id":38094545,"uuid":"166209963","full_name":"UiPath/angular-components","owner":"UiPath","description":"Angular components for r$ch web applications","archived":false,"fork":false,"pushed_at":"2024-04-22T23:55:13.000Z","size":30944,"stargazers_count":40,"open_issues_count":8,"forks_count":24,"subscribers_count":89,"default_branch":"master","last_synced_at":"2025-04-24T06:48:09.622Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"https://platform.uipath.com","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/UiPath.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2019-01-17T10:50:25.000Z","updated_at":"2024-07-07T13:16:32.000Z","dependencies_parsed_at":"2023-11-12T21:30:05.592Z","dependency_job_id":"f0269003-fd5d-40a9-856f-434a6abd4ffe","html_url":"https://github.com/UiPath/angular-components","commit_stats":null,"previous_names":[],"tags_count":219,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/UiPath%2Fangular-components","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/UiPath%2Fangular-components/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/UiPath%2Fangular-components/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/UiPath%2Fangular-components/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/UiPath","download_url":"https://codeload.github.com/UiPath/angular-components/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":252283571,"owners_count":21723499,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-13T03:29:19.068Z","updated_at":"2025-05-04T03:30:52.402Z","avatar_url":"https://github.com/UiPath.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003cimg src=\"https://raw.githubusercontent.com/UiPath/angular-components/master/logo.png\" width=\"135\" /\u003e\n\n# Angular Components Library\n\n**This repo will be used only for support fixes.**\n\n`@uipath/angular` was moved into [apollo-design-system](https://github.com/UiPath/apollo-design-system/tree/master/packages/apollo-angular-components).\n\nNew features will move implemented in the new package `@uipath/apollo-angular`.\n\nSteps to migrate to new package can be found [here](https://github.com/UiPath/apollo-design-system/tree/master/packages/apollo-angular-components#migration-from-uipathangular-and-uipathangular-internal-to-uipathapollo-angular).\n\nA great set of reusable `@angular` components, directives and testing utilities.\n\nOne of our main goals is to allow easy integration with the great collection of components already provided by the `@angular/material` team and to build everything with the following in mind:\n\n- 🤘 a11y\n- 🚀 performance\n- 💖 look and feel\n\n[![npm](https://img.shields.io/npm/v/@uipath/angular.svg)](https://www.npmjs.com/package/@uipath/angular)\n[![Build Status](https://uipath.visualstudio.com/angular-components/_apis/build/status/UiPath.angular-components?branchName=master)](https://uipath.visualstudio.com/angular-components/_build/latest?definitionId=387\u0026branchName=master)\n[![Test Coverage](https://api.codeclimate.com/v1/badges/61117dc99c96535bbfb2/test_coverage)](https://codeclimate.com/github/UiPath/angular-components/test_coverage)\n[![Maintainability](https://api.codeclimate.com/v1/badges/61117dc99c96535bbfb2/maintainability)](https://codeclimate.com/github/UiPath/angular-components/maintainability)\n[![License](https://badgen.net/badge/license/MIT/blue)]()\n\n## Browser Support\n\n| [\u003cimg src=\"https://raw.githubusercontent.com/alrra/browser-logos/master/src/edge/edge_48x48.png\" alt=\"IE / Edge\" width=\"24px\" height=\"24px\" /\u003e](http://godban.github.io/browsers-support-badges/)\u003c/br\u003eIE / Edge | [\u003cimg src=\"https://raw.githubusercontent.com/alrra/browser-logos/master/src/firefox/firefox_48x48.png\" alt=\"Firefox\" width=\"24px\" height=\"24px\" /\u003e](http://godban.github.io/browsers-support-badges/)\u003c/br\u003eFirefox | [\u003cimg src=\"https://raw.githubusercontent.com/alrra/browser-logos/master/src/chrome/chrome_48x48.png\" alt=\"Chrome\" width=\"24px\" height=\"24px\" /\u003e](http://godban.github.io/browsers-support-badges/)\u003c/br\u003eChrome | [\u003cimg src=\"https://raw.githubusercontent.com/alrra/browser-logos/master/src/safari/safari_48x48.png\" alt=\"Safari\" width=\"24px\" height=\"24px\" /\u003e](http://godban.github.io/browsers-support-badges/)\u003c/br\u003eSafari |\n| --------- | --------- | --------- | --------- |\n| IE11, Edge| last 2 versions| last 2 versions| last 2 versions\n\n## Installation\n\n`npm i @uipath/angular`\n\n## Documentation\n\nVisit our docs page [here](https://uipath.github.io/angular-components). Thanks go to the [@compodoc](https://compodoc.app/) team! 👌\n\n# Contributing\n\n### Commit Messages\n\nWe initially started off by using a `custom` commit message convention, now that we've gone OS, we realize it will be much easier for everyone if we adhere to the `conventional-commit` standard.\n\nThe project comes preconfigured with `commitlint` and `husky` hooks in order to automate checks.\n\nAnother advantage of `conventional-commits` is that it will allow us to later on integrate `semantic-release` with ease.\n\n### Conflict Resolution\n\nWe all know that once you open a `PR`, it sometimes goes through a rigorous code review process. Sometimes, due to this delay, we end up with a `PR` that has `conflicts`.\n\nIn this scenarios, we're usually used to either `merge` or `rebase`.\n\nWe personally prefer that branches get `rebased`, and usually stay away from `merge` commits as they mostly end up polluting the history needlessly. At this point, most of you are probabily thinking: `Yeah, but it's not a good practice to rebase if multiple people are working on the same branch!`.\n\nTrue, it's not recommended to `rebase` when multiple people are active on the same `branch`, but in this scenario `git` offers a very elegant solution: `fixup` commits. By using `fixup commits`, the branch can later go through an `interactive rebase` once the `review` process is done and the `PR` is approved.\n\nFor example: after you make your changes and stage them you can run a `git commit --fixup HEAD~` to add the changes in the last but one commit. Before the merge, you can then simply `git rebase -i \u003cref\u003e --autosquash` and every change will be squashed in the correct commit.\n\n### Environment setup\nBefore contributing you will need to add the environment variable GH_NPM_REGISTRY_TOKEN with a dummy (empty) value. We are distributing the packages both publicly and internally and unfortunately npmrc uses an ini file format which doesn't allows us to provide a fallback automatically.\n\n### Why?\n\n**Q:** Why all the hassle, does it really matter?\n\n**A:** We've seen too many branches where `merge commits` get introduced without a good reason, too many branches that have almost the same number `merge commits` as `commits` so we want to enforce a git usage guidline that promotes responsibility. 🐱‍👤\n\n**Q:** But I want to integrate a branch, not yet merged and implement a new feature.\n\n**A:** In this scenario, you have the `master` branch, and the `feature` branch that you depend upon. What we do in this case, is create a local branch where we merge the required `feature` branch into `master` and start our branch from there. Once the `feature` branch we depend upon, gets merged into `master`, we `rebase` over master. Easy peasy! 🤓\n\n**Q:** But what if I just want to add a feature?\n\n**A:** We think that in software, it's not just about the feature, it's also about the fact that others will later on need to support that feature or modify it, having a good historical track helps everyone better understand the evolution of the codebase.\n\n## Coming Up (most likely v1)\n\n- Getting Started / Contribution Guidlines\n- Enhanced Component Demo's\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fuipath%2Fangular-components","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fuipath%2Fangular-components","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fuipath%2Fangular-components/lists"}