What's new in Telosys Core version 3.1.0

All the improvements described below are implemented in Telosys-Core

All these features will be used in the upcoming version 3.1.0 of Telosys-CLI and Telosys-Eclipse-Plugin

 

Code generation for 'Go language' 

Go language is now supported as an 'explicit target language' by Telosys.

To define 'Go' as the target language in a template file use this directive :
  #set ( $env.language = 'Go' )

For more information about 'Go' specificities see the documentation
http://www.telosys.org/doc/telosys-core-v310/languages/language-go.html

 

Code generation for 'PHP language'

PHP language is now supported as an 'explicit target language' by Telosys.

To define 'PHP' as the target language in a template file use this directive :
  #set ( $env.language = 'PHP' )

For more information about 'PHP' specificities see the documentation
http://www.telosys.org/doc/telosys-core-v310/languages/language-php.html

Table comment is now available in $entity object

You can use it in a template (.vm file) with  $entity.databaseComment
The comment comes from the database, hence it is only available for a DB model
otherwise it returns a void string.

GitHub user authentication allows to extend the API rate limit

For unauthenticated requests, the GitHub API allows only 60 requests per hour (for a given IP address). That is very limited especially if the IP address is shared by many users (with a proxy for example).
For more information see : https://developer.github.com/v3/rate_limit/
This can cause errors when installing bundles.

Telosys 3.1.0 now supports GitHub authentication ( user + password )
When you're authenticated you can send up to 5000 requests per hour .

How to generate files outside the current location

With the default configuration the telosys tooling is located in the project folder where the files are generated.

It's possible to change the configuration in order to specify a specific destination for the generated files.

With this configuration, it is possible to generate files anywhere.
You just have to indicate the destination directory.

If you are using Telosys-CLI

  Use the command "ecfg" (Edit Configuration) to edit the "telosys-tools.cfg" file.

  Define the "SpecificDestinationFolder" property
  Examples :
  SpecificDestinationFolder=C\:\\dir1\\dir2
  SpecificDestinationFolder=/dir1/dir2

If you are using Telosys Eclipse Plugin 

  In the project workspace open the "Telosys Tools properties editor"
  from the menu : "File" - "Properties" - "Telosys Tools"
  or with a Right-Click on the project "Properties" - "Telosys Tools"

  Select the "Advanced" tab and set the specific location for code generation

Hence it's possible to create a "General project" just for Telosys tooling and use it to generate outside the workspace.