Uses djantajs runtime compiler that extract all known annotation from your code and then generate the .djanta-rc.json configuration.
djantajs-compiler-rc is the tool magical provided to make djantajs server to boot less than a couple of seconds instead of minutes. By using this annotation framework with your djantajs bundle, your project will be parsed at build lifecycle and then generate .djanta-rc.json. If that's not enough for you, it's also the most powerful and easy-to-use.
This version of the module requires at least npm >=4.6.0 and node >=6.0.0
If you haven't used npm before, be sure to check out the Getting Started guide. Once you're familiar with that process, you may install this module with this command:
Install with npm:
npm i @djanta/djantajs-compiler-rc --save[-S]Once you install the compiler, you might also want the .djanta-rc.json to be automatically generatated. Therefore, we've provided the Grunt task which you can install as follow:
npm i grunt-djantajs-compiler --save-devThe Grunt task configuration is available at:
However, as to day, the Gulp task generator is coming soon ...
Once this module has been sucessfully installed and well configured, it may be enabled and ready to be used inside your project with this line of JavaScript:
let { Handler, ModuleBase } = require('@djanta/djantajs-compiler-rc');In the following sections, we'll learn how to deploy the core platform provided annotions to describe your djantaJS compliant application.
In your project's Gruntfile, add a section named bundlerc to the data object passed into grunt.initConfig().
@bundleThe bundle annotation has been provided and will only be declared with class level retention.
Type: String
Default value: ${package.name}
Required: false
A litteral string value which can better introduce your bundle name. By default, the npm manifest name will be used instead.
Type: String
Default value: ${package.version}
Required: false
A string value that'll to define the latest version of your bundle. This has been instroduced due of some reasons when certains application
like to diverge their functional version from the technical version i.e: package.json. However, this version must follow the sementic versioning taxinomy: <major>.<minor>.<patch>
Type: Boolean
Default value: true
Required: false
A boolean value that you can set to falseto exclude the all bundle to be scaned at build time or to be deploy at runtime. If unspecified, the default value is set to true
Type: Number
Default value: 1000
Required: false
A boolean value that you can set to falseto exclude the all bundle to be scaned at build time or to be deploy at runtime. If unspecified, the default value is set to true
Type: Array
Default value: ``
Required: false
An array value to list which other bundle(s) this bundle depends on.
Type: Array
Default value: ``
Required: false
An array of short tag list which fit well your bundle.
/**
* @bundle(name: 'MyCustomizedBundleName', version='1.0.1', enabled=true, order=1,
* tags=['testing', 'documentation'],
* homepage='www.djantajs.io'
* imports=['BundleOne', 'BundleTow', '...'],
* author='DJANTA, LLC'
* )
*/
module.exports = class MyCustomizedBundle {
/**
* Qualified default class constructor
*/
constructor () {}
// ... can implement anything you'd like here.
}{
"package": "my-real-npm-package-name", //mandatory extracted from your package.json
"name": "MyCustomizedBundleName",
"homepage": "www.djantajs.io",
"version": "1.0.1",
"author": "DJANTA, LLC",
"imports": "['BundleOne', 'BundleTow', '...']",
"tags": "['testing', 'documentation']"
}The following annotation called plugin represent one of the most important, powerful and the most used annotation we've ever provided.
Therefore, this's basically the annotion you'll be uising to describe each service provided by your djantajs contribution.
@pluginThe plugin annotation has been provided as class retention level.
Type: String
Default value:
Required: true
A litteral string value that'll be use to lookup for your service implementation across the platform. Basically this value should be consider as uniq key.
Type: String
Default value: 1.0.0
Required: false
A string value that'll to define the latest version of your service. This has been instroduced as a helper to handle the service versioning or upgrade. This'll be useful to ensure your service migration.
However, this version must follow the sementic versioning taxinomy: <major>.<minor>.<patch>
Type: Array
Default value:
Required: false
An array value to list which other service this service is pending on.
Type: Array
Default value:
Required: false
An array of tag list to shortly describe the service purpose.
Type: Array
Default value:
Required: false
An array of porte where any 3rd party can enrich your service at.
Type: String
Default value:
Required: true
A litteral string value that'll be use to lookup for your service implementation across the platform. Basically this value should be consider as uniq key.
Type: String
Default value:
Required: true
A litteral string value that'll be use to lookup for your service implementation across the platform. Basically this value should be consider as uniq key.
Type: Array
Default value:
Required: false
An array of tag list to shortly describe the service purpose.
const { Plugin } = require ('@djanta/djantajs-runtime');
/**
* So far, the plugin annotation might take place you class definition level as follow:
*
* @plugin(name="CarRentalService", version="1.0.1", engine=[">=7.6.0"],
* imports=["MyTiersBillingService", "MyS3BillStorageService@>=0.2.8"],
* tags=["finance", "trading", "accounting", "payment"],
* portes=[@porte(name='searchEngineManager', enabled=true, description='Qualified extension where anyone can contribute their car search engine'),
* @porte(name='quotes', enabled=true, description='Qualified extension where any outsider can contribute their pricing service')
* ],
* description="This's how you can provide your service to enrich the ecosytem",
* authors=["DJANTA, LLC"],
* settings=[@setting(name='my-setting-identifier', value=#{any value goes here}, description='Each setting description here!')]
* )
*/
module.exports = class CarRentalService extends Plugin {
/**
* Qualified default explicit constructor declaration
* @param {*} options construction plugin configurable option
*/
constructor (options = {}) {
super (options);
}
/**
* Runtime invocable lifecycle ....
*/
init (options = {}) {
super.init(options);
// Here i can do anything i want to initialize my plugin
}
};{
"plugins": [
{
"name": "CarRentalService",
"enabled": true,
"version": "1.0.1",
"order": -1,
"engine": [
">=7.6.0"
],
"tags": [
"finance",
"trading",
"accounting",
"payment"
],
"imports": ["MyS3BillStorageService@>=0.2.8", "MyTiersBillingService"],
"portes": [
{
"name": "searchEngineManager",
"enabled": true,
"description": "Qualified extension where anyone can contribute their car search engine"
},
{
"name": "quotes",
"enabled": true,
"description": "Qualified extension where any outsider can contribute their pricing service"
}
],
"settings": [
{
"name": "my-setting-identifier",
"value": "#{any value goes here}",
"description": "Each setting description here!"
}
],
"description": "This's how you can provide your service to enrich the ecosytem",
"class": "services/cars-rental-service.js"
}
]
}This annotion must be used in conjugaison with the @plugin annotation to define the specified porte e.g contribution point provided by the current plugin.
@porteThe porte annotation has been provided as class retention level.
Type: String
Default value:
Required: true
A litteral string value to define the porte name. Note the prote given name mnust be uniq per service.
Type: Boolean
Default value: true
Required: false
A boolean value to enable or desable the porte accessibility. This value can just be set to false to desable the porte provisioning.
Type: String
Default value:
Required: false
A litteral string value to describle the given porte usage and goal. This'll be useful to other developers the purpose of the current porte.
let { Plugin } = require ('@djanta/djantajs-runtime');
/**
* So far, the plugin annotation might take place you class definition level as follow:
* @plugin(name="MyPorteDemoService", version="1.0.1", engine=[">=7.6.0"],
* portes=[@porte(name='my-feature-porte', enabled=true,
* description='Anyone can now contribute to my service through this porte')
* ]
* )
*/
module.exports = class MyPorteDemoServiceClass extends Plugin {
/**
* Qualified default class constructor
* @param {*} options construction plugin configurable option
*/
constructor(options = {}){
super(options);
}
}{
"plugins": [
{
"name": "MyPorteDemoService",
"enabled": true,
"version": "1.0.1",
"order": -1,
"engine": [
">=7.6.0"
],
"portes": [
{
"name": "my-feature-porte",
"enabled": true,
"description": "Anyone can now contribute to my service through this porte"
}
]
}
]
}This annotion must be used in conjugaison with the @plugin annotation to define the providedplugin default configuration.
@settingThe porte annotation has been provided as class retention level.
Type: String
Default value:
Required: true
A litteral string value to define the setting mapping name.
Type: String
Default value:
Required: false
A litteral string value to describle the given setting usage and goal. This'll be useful to other developers the purpose of the current porte.
Type: #Any
Default value:
Required: true
Any data type you'd like to map with the given name.
const { Plugin } = require ('@djanta/djantajs-runtime');
/**
* So far, the plugin annotation might take place you class definition level as follow:
* @plugin(name="MyPorteDemoService", version="1.0.1", engine=[">=7.6.0"],
* settings=[@setting(name='my-setting-identifier', value=#{any value goes here}, description='Each setting description here!')]
* )
*/
module.exports = class MySettingDemoServiceClass extends Plugin {
/**
* Qualified default class constructor
* @param {*} options construction plugin configurable option
*/
constructor(options = {}){
super(options);
}
}{
"plugins": [
{
"name": "MyPorteDemoService",
"enabled": true,
"version": "1.0.1",
"order": -1,
"engine": [
">=7.6.0"
],
"settings": [
{
"name": "my-setting-identifier",
"value": "#{any value goes here}",
"description": "Each setting description here!"
}
]
}
]
}In your project's Gruntfile, add a section named bundlerc to the data object passed into grunt.initConfig().
In your project's Gruntfile, add a section named bundlerc to the data object passed into grunt.initConfig().
Install dev dependencies:
$ npm i -d && npm testPull requests and stars are always welcome. For bugs and feature requests, please create an issue.
- First things first, please make sure to run
npm cache clear, then donpm i djantajs-compiler-rc --save[-dev]. If that doesn't clear things up, try #2. - Create an issue. We'd love to help, so please be sure to provide as much detail as possible, including:
- version of djantajs-compiler-rc
- platform
- any error messages or other information that might be useful.
(Nothing yet)
Stanislas Koffi ASSOUTOVI
Copyright © 2015-2018 DJANTA, LLC
Released under the MIT license.