This sample contains multiple pre-built Linx functions which allow you to quickly connect and make HTTP requests the GitHub REST API. These 'connector' functions have been built and tested to handle to the specifics of interacting with the various GitHub API methods and resources. You can copy and use these functions in your own Linx Solution to accelerate development.
The goal of this Linx Solution is to ultimately include custom built connector functions for all the methods of the GitHub API specified here.
For a full list of the current connector functions contained in the sample, take a look at the wiki.
- Install the Linx Designer, download it here.
- Open the sample Solution (.lsoz) in your Linx Designer.
- Right-click on the GitHubAPI folder in the Solution Explorer.
- Select Copy.
- Open your own Solution.
- Right-click on your Solution Explorer and click Paste.
- A validation error will occur referencing the missing Solution setting values.
- Copy and paste the setting names and values from the Sample solution into your own Solution.
- The validation messages will dissapear and you can now drag the required connector functions into your own custom functions.
Authentication of requests is achieved via access tokens, the functions take in the "access token" used in the request as an input parameter at runtime, which is then added to the header of the request.
This "access token" needs to be passed in to each function by you, this could be retrieved from a database, file or external service.
You're able to generate and retrieve your token from an external authentication service or, alternatively, you're able to host your own Linx authentication service with the linx-oauth-token-service project on GitHub.
This sample contains generic "connector" functions which can be imported and used in your own Linx Solution.
For a full list of the implemented methods, have a look at the wiki.
Each connector function in the Solution follows the below structure:
- Takes in an "access token" value as an input parameter.
- Takes in any data used for the request parameters such as query, path or requestBody values.
- Removed any empty fields and transforms the inputs into a JSON string.
- Makes a HTTP request to the API and returns a string response.
- The response body string is then parsed using a JSON reader.
- The content of the response body is then returned from the function as the result object type.
These functions do not persist any data and only return or send data that is received at runtime, therefore you must add your own data persistence layer if required.
A 'Tests' project has been included in the sample Linx Solution to demonstrate the usage of the connector functions. This 'Tests' project contains custom built functions which execute some of the connector function's related to the different areas of the GitHub API as a demonstration. These automated tests will result in mock data being pushed and retrieved from your instance of GitHub. The 'access token' needed for the functions are passed in from a Solution Setting value which you can update with your access token to run the tests.
If there are specific GitHub API operations that you would like to see in the sample, contact support@linx.software.
For questions and issues please ask the Linx community or use the Slack channel.