With the release of the new version of <aestro, calls to enter and capture platform credentials are available. You will need to implement the following methods:

• getCredential
• create credential
• getCredentials
• createCredentials
• updateCredential
• getValueCredential
• deleteCredential

To develop in Typescript it is necessary for the project to create a package in NPM called Types, for developers who use the language to be able to visualize the types of parameters, returns and so on.

Acceptance criteria

• Package Types in Npm.
• Being able to recognize what the function returns directly in the IDE.

With the release of the Maestro version supporting the Error feature, it will be necessary to create functions that communicate with this module:

• createError
• createAttachment
• createScreenshot

It is necessary to send the following parameters:

• taskId
• type (error type)
• message(error)
• stackTrace
• language (javascript/typescript)
• tags

issue #1

This PR was opened to make the developer's life easier and to integrate the sdk with the most modern IDEs with the return types of the Sdk class methods.

Added some TODOs in the code that will be performed after the inclusion of fixes in the Maestro API.

issue #2

This PR was opened to meet the need to have a pipeline that executes lint in the project in open pull requests, thus ensuring the quality and standardization of the code.

In addition to helping in the future implementation of test execution by making the standardized pipeline.

In each pull request opening it is necessary to run "lint" to guarantee the code quality. If there is something wrong/out of standard, the pull request is blocked until the adjustment is made.

It is necessary to implement interface in the project to use typescript in the best possible way.

For this it will be necessary to do a study on the return of the Maestro API and based on that create the necessary interfaces. Interesting content explaining in a simple way [how to create customizable types with typescript.

(https://www.typescriptlang.org/docs/handbook/interfaces.htmlt)

Acceptance criteria

• Being able to recognize what the function returns directly in the IDE.

For the project to maintain its quality standard, it is necessary that all classes/methods/functions have some referring unit test.

This serves to predict behavior and ensure pre- and post-delivery functionality of the feature in question.

We will use the Jest library to create the tests.

Acceptance criteria

• Have a test coverage of more than 86%.
• All tested functions must have their success and error test.
• Each test has an execution timeout of 50ms.
• Tests with duplication of logic will not be accepted.
• The test name must be understandable

To be able to create effective unit tests to improve code quality, it is necessary to separate the responsibilities contained in the BotMaestroSdk class into classes.

Following the controllers available on swagger

Acceptance criteria

• Have a class specialized in user.
• Have a class specialized in tasks/automations.
• Have a class specialized in logs.
• Have a class specialized in alerts.
• Have a class specializing in artifacts.
• In the BotMaestroSdk class it is necessary that the methods remain the same.

To make it easier for the user to use it is interesting to implement jsdoc so that there is a concise reading of what the function/class/method executes, receives and returns interactively with the IDE.

To learn more about jsdoc on Typescript

Acceptance criteria

• Be able to read the description of the methods through the IDE.