Merge pull request #47 from thefill/feature/ChangeServiceExport

Feature/change service export

README.md

@@ -54,7 +54,7 @@ Jetli allows you to inject consistently classes, functions and primitives across
 
 Injecting instances of classes is trivial with jetli - just use 'get' method without any additional options.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 class Attack {
     constructor(){
@@ -78,7 +78,7 @@ Functions, already instantiated objects or primitive values like array, string a
 
 Registration is provided via 'set' method and requires you to provide string token that identifies the injectable element.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 class Attack {
     constructor(){
@@ -101,7 +101,7 @@ fighter2.punch();</pre>
 
 As explained in previous example primitives can be easily used across your applications with associated string id provided during registration.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 const someNumber = 123;
 const someString = 'punch';
@@ -124,7 +124,7 @@ console.log(injectedArray);</pre>
 
 To use Jetli to full extend implement services that expose init method. This method is the safest place to use Jelit injector inside injectable services.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 jetli.set('someNumber', 123);
 
@@ -151,7 +151,7 @@ fighter2.punch();</pre>
 
 Have enough of overhead when all those services initialises at once? Register them and request initialisation only when injection is requested.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 class Attack {
     constructor(){
@@ -174,7 +174,7 @@ fighter2.punch();</pre>
 
 ### Pass arguments to services constructor
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 class Attack {
     constructor(id){
@@ -198,7 +198,7 @@ fighter2.punch();</pre>
 
 Jetli uses battle-tested method to fight 'cyclic dependencies' - optional initialisation callback. Injector searches for optional init method to call it and as an argument to provide instance of injector itself. This method provide safe moment to inject all dependencies required by service - you can be sure that all dependencies will be already initialised.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 class ServiceA {
     init(jetli){
@@ -240,7 +240,7 @@ serviceB.getId();</pre>
 
 Its rather trivial to mock module dependencies if you have total control whats injected where, right? ith Jetli you can reset any previously registered/injected dependencies and introduce your own mocks / stubs.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 class Attack {
     constructor(){

package.json

@@ -1,6 +1,6 @@
 {
     "name": "jetli",
-    "version": "0.0.7",
+    "version": "1.0.0",
     "description": "Dependency injector",
     "main": "dist/cjs/index.js",
     "module": "dist/esm/index.js",

src/docs-partials/readme.body.md

@@ -36,7 +36,7 @@ Jetli allows you to inject consistently classes, functions and primitives across
 
 Injecting instances of classes is trivial with jetli - just use 'get' method without any additional options.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 class Attack {
     constructor(){
@@ -60,7 +60,7 @@ Functions, already instantiated objects or primitive values like array, string a
 
 Registration is provided via 'set' method and requires you to provide string token that identifies the injectable element.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 class Attack {
     constructor(){
@@ -83,7 +83,7 @@ fighter2.punch();</pre>
 
 As explained in previous example primitives can be easily used across your applications with associated string id provided during registration.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 const someNumber = 123;
 const someString = 'punch';
@@ -106,7 +106,7 @@ console.log(injectedArray);</pre>
 
 To use Jetli to full extend implement services that expose init method. This method is the safest place to use Jelit injector inside injectable services.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 jetli.set('someNumber', 123);
 
@@ -133,7 +133,7 @@ fighter2.punch();</pre>
 
 Have enough of overhead when all those services initialises at once? Register them and request initialisation only when injection is requested.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 class Attack {
     constructor(){
@@ -156,7 +156,7 @@ fighter2.punch();</pre>
 
 ### Pass arguments to services constructor
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 class Attack {
     constructor(id){
@@ -180,7 +180,7 @@ fighter2.punch();</pre>
 
 Jetli uses battle-tested method to fight 'cyclic dependencies' - optional initialisation callback. Injector searches for optional init method to call it and as an argument to provide instance of injector itself. This method provide safe moment to inject all dependencies required by service - you can be sure that all dependencies will be already initialised.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 class ServiceA {
     init(jetli){
@@ -222,7 +222,7 @@ serviceB.getId();</pre>
 
 Its rather trivial to mock module dependencies if you have total control whats injected where, right? ith Jetli you can reset any previously registered/injected dependencies and introduce your own mocks / stubs.
 
-<pre class="runkit-source">const jetli = require('jetli@0.0.6').jetli;
+<pre class="runkit-source">const jetli = require('jetli@0.0.8').jetli;
 
 class Attack {
     constructor(){

src/index.ts

@@ -1,7 +1,4 @@
 // Export classes and interfaces just in case
 export * from './interfaces';
 export * from './classes';
-
-// make service exported as default for the easiness of usage
-import {jetli} from './services';
-export default jetli;
+export * from './services';