Development Tools

You can use various development tools for creating, testing, and debugging your integration packages.

In this document:

CLI Tools

As an alternative to an IDE, you can use APS tools in the command line interface: the CLI tools.

  • The project validation tool (aps lint) detects errors and other issues and validates a compressed package. It displays error and warning messages with references to the respective line of code. For example, the following command validates the specified APS package:

    $ aps lint Simplest_demo_project-1.0-0.app.zip
    
    Validating package for compatibility with APSC 2.2
    Minimal compatible APSC version - 2.0
    APP-META.xml:6: Error aps021: '/application/homepage' element is empty. Package metadata
    must contain a URL of the application home page.
    
  • The project building tool (aps build) validates the project, and, if there are no errors, creates a compressed package. If it discovers an error, you will see an error message that specifies the error cause and place. Start this command as in the following example:

    $ aps build VPScloud/
    

APS Fiddle

APS Fiddle is an online tool similar to jsFiddle. It is helpful when creating, testing, and debugging the HTML and JavaScript used in the UI of your integration package in your browser, including:

  • Layout and hierarchy of widgets

  • Interaction of widgets

  • The algorithm used to process and present application data

The tool identifies JavaScript errors and issues and displays them with helpful annotations in real time.

Schema Builder

To verify the valid declaration of metadata in your PHP scripts, you can run the following command in your local environment that contains the APS PHP runtime:

$ php scripts/context.php '$schema'