@coveops/microsoft-dynamics-365-service
v1.0.1
Published
Disclaimer: This component was built by the community at large and is not an official Coveo JSUI Component. Use this component at your own risk.
Downloads
4
Maintainers
Keywords
Readme
microsoft-dynamics-365-service
Disclaimer: This component was built by the community at large and is not an official Coveo JSUI Component. Use this component at your own risk.
Getting Started
- Install the component into your project.
npm i @coveops/microsoft-dynamics-365-service
- Use the Component or extend it
Typescript:
import { microsoft-dynamics-365-service, Imicrosoft-dynamics-365-serviceOptions } from '@coveops/microsoft-dynamics-365-service';
Javascript
const microsoft-dynamics-365-service = require('@coveops/microsoft-dynamics-365-service').microsoft-dynamics-365-service;
- You can also expose the component alongside other components being built in your project.
export * from '@coveops/microsoft-dynamics-365-service'
- Or for quick testing, you can add the script from unpkg
<script src="https://unpkg.com/@coveops/microsoft-dynamics-365-service@latest/dist/index.min.js"></script>
Disclaimer: Unpkg should be used for testing but not for production.
- Include the component in your template as follows:
Place the component in your markup:
<div class="Coveomicrosoft-dynamics-365-service"></div>
Extending
Extending the component can be done as follows:
import { microsoft-dynamics-365-service, Imicrosoft-dynamics-365-serviceOptions } from "@coveops/microsoft-dynamics-365-service";
export interface IExtendedmicrosoft-dynamics-365-serviceOptions extends Imicrosoft-dynamics-365-serviceOptions {}
export class Extendedmicrosoft-dynamics-365-service extends microsoft-dynamics-365-service {}
Contribute
- Clone the project
- Copy
.env.dist
to.env
and update the COVEO_ORG_ID and COVEO_TOKEN fields in the.env
file to use your Coveo credentials and SERVER_PORT to configure the port of the sandbox - it will use 8080 by default. - Build the code base:
npm run build
- Serve the sandbox for live development
npm run serve