Obtaining Source Code

To obtain the source code of the components, refer to the list of available packages and download the source code as a set of Git repositories.

The source code is available only for commercial-license holders and you will be asked to enter your credentials.

Source Repositories

1. To obtain the full source code for each package, clone a repository from the Kendo UI for Angular Git mirror. The repositories contain the complete revision history of the official releases.

   Copy Code// The URLs of the available repositories for download follow the
   // https://kendo.git.progress.com/<package name without scope>.git pattern.
   // For the list of the package names you can use in this URL pattern,
   // refer to the section on the list of repositories below.
   
   git clone https://kendo.git.progress.com/kendo-angular-buttons.git

2. To update your clone, run git pull. The mirror repositories are updated daily.

Tags

The source repositories contain tags for each official release—for example, "v1.0.0" or "v1.1.0". To get the full list of all tags, run git tag.

Branches

The source repositories contain a single master branch. It corresponds to the latest NPM dist-tag and represents the current official release of the package that you normally get by running npm install.

Building from Source

You can use the repositories for building modified versions of the official packages. However, the Kendo UI license prohibits the redistribution of modified versions of the packages.

1. Replace the metadata in the package.json file to make your package name unique.

Copy Code```json
{
  "name": "my-lovely-kendo-angular-buttons",
  "description": "Customized buttons package",
  "version": "1.0.0"
}
```

1. Replace flatModuleId with the package name in tsconfig.es.json and tsconfig.es2015.json.
2. Run npm install to install all developer dependencies.
3. Run npm run build-package && npm pack to produce an NPM package.
4. Use the newly built package in your application.

Copy Code```sh
    npm install --save my-lovely-kendo-angular-buttons-1.0.0.tgz
```

Submitting Your Credentials

To avoid being asked for your credentials while you clone a repository, store them.

Choosing Storage Options

To store your credentials, either:

• Cache your credentials by storing them as plain text in a .netrc file, or
• Store your credentials by using the Git credential helpers. For detailed information on how to do this, refer to Stack Overflow and follow the discussion on skipping the password typing.

Storing on Windows

1. Create a text file called _netrc in your home directory—for example, c:\users\jane\_netrc.

2. Declare a HOME environment variable.

   Copy CodeC:> SETX HOME %USERPROFILE%

3. Add your credentials by applying the following format:

   Copy Codemachine kendo.git.progress.com
       login my-progress.identity@example.com
       password mysecret

If your home directory contains spaces in its path, Git might experience problems when it tries to access it—for example, c:\Documents and Settings\jane. To avoid such issues, set your %HOME% environment variable so that it points to a directory and has no spaces in its name.

Storing on Linux, OS X, and Unix-Like Systems

1. In your home directory, create a file called .netrc (~/.netrc). Modify the file permissions so that the file is readable only for you.

   Copy Codetouch ~/.netrc
   chmod 0600 ~/.netrc

2. Add your credentials to the ~/.netrc file by using the following format:

   Copy Codemachine kendo.git.progress.com
       login my-progress.identity@example.com
       password mysecret

Troubleshooting

This section provides solutions for common issues you might encounter while cloning the source code repositories.

SSL Issues Occur on Windows

You might see the following error message:

Copy Codefatal: unable to access 'https://kendo.git.progress.com/kendo-angular-buttons.git/': SSL certificate problem: unable to get local issuer certificate

Cause

The underlying Git installation is missing the certificate bundle.

Solution

Follow the steps in the Adding a corporate (or self-signed) certificate authority to git.exe’s store MSDN blog post.

If you have to use the @ symbol in the URL because of, for example, network restrictions or admin rules, encode it as https://firstname.lasname%40domain.com@kendo.git.progress.com/kendo-angular-buttons.git.

List of Repositories

The following list includes the package names of all source repositories that are available for download. For more information on how to obtain their code and include them in the URL pattern, refer to the section on source repositories.

• kendo-angular-buttons
• kendo-angular-charts
• kendo-angular-common
• kendo-angular-conversational-ui
• kendo-angular-dateinputs
• kendo-angular-dialog
• kendo-angular-dropdowns
• kendo-angular-editor
• kendo-angular-excel-export
• kendo-angular-gauges
• kendo-angular-grid
• kendo-angular-icons
• kendo-angular-indicators
• kendo-angular-inputs
• kendo-angular-intl
• kendo-angular-l10n
• kendo-angular-label
• kendo-angular-layout
• kendo-angular-menu
• kendo-angular-navigation
• kendo-angular-notification
• kendo-angular-pager
• kendo-angular-pdf-export
• kendo-angular-popup
• kendo-angular-progressbar
• kendo-angular-ripple
• kendo-angular-scheduler
• kendo-angular-scrollview
• kendo-angular-sortable
• kendo-angular-toolbar
• kendo-angular-tooltip
• kendo-angular-treelist
• kendo-angular-treeview
• kendo-angular-upload
• kendo-charts
• kendo-data-query
• kendo-date-math
• kendo-drawing
• kendo-file-saver
• kendo-intl
• kendo-ooxml
• kendo-ripple

Suggested Links

• Getting Started with Kendo UI for Angular