### Install ADAC API Client
Source: https://github.com/realtimeregister/adac-api-client/blob/master/README.md
Installs the ADAC API client using either Yarn or npm package managers. This is the first step to integrating the client into your project.
```bash
yarn add @realtimeregister/adac-api-client
```
```bash
npm install @realtimeregister/adac-api-client
```
--------------------------------
### Vue with Bootstrap 5: ADAC API Client Integration
Source: https://github.com/realtimeregister/adac-api-client/wiki/Examples
Illustrates integrating the ADAC API client into a Vue.js application styled with Bootstrap 5. This example features a more structured layout for domain input, category selection, and results display, utilizing Bootstrap components for styling.
```vue
Check if your domain is available
.com
Results
{{ domain.domain_name }}
Suggestions
{{suggestion.domain_name}}
```
--------------------------------
### Vue: Basic ADAC API Client Integration
Source: https://github.com/realtimeregister/adac-api-client/wiki/Examples
Demonstrates a basic integration of the ADAC API client in a Vue.js application. It includes input fields for domain search, category selection, and displays results and suggestions. Requires the '@realtimeregister/adac-api-client' package and a debounce utility.
```vue
{{result.domain_name}}
{{suggestion.domain_name}}
```
--------------------------------
### Build ADAC API Client
Source: https://github.com/realtimeregister/adac-api-client/blob/master/README.md
Commands for building the ADAC API client. 'yarn build' compiles for production, while 'yarn dev' builds for development with watch mode enabled for continuous updates.
```bash
yarn build
```
```bash
yarn dev
```
--------------------------------
### Semantic Release Commit Type Mapping
Source: https://github.com/realtimeregister/adac-api-client/blob/master/CONTRIBUTING.md
Illustrates how different commit types are mapped to release types (minor, patch, major) by semantic-release, based on conventional commit standards. This ensures proper versioning and changelog generation.
```text
- `feat:` would be associated with a `minor` release;
- `fix:` would be associated with a `patch` release;
- If `BREAKING CHANGE` is included in the commit message, a `major` release will be triggered;
- etc.
```
--------------------------------
### Conventional Commit Scopes for adac-api-client
Source: https://github.com/realtimeregister/adac-api-client/blob/master/CONTRIBUTING.md
Defines the allowed scopes for commit messages in the adac-api-client project, aligning with conventional commit guidelines. These scopes help categorize changes for automated release management.
```text
- `api` - Changes to API logic, e.g. connections and calls;
- `client` - Changes related to the ADAC client/class;
- none/empty - changes that don't fall under any of the scopes above, typically seen with type `chore` and `refactor`.
```
=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.