Summer '18 Release

LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2017 Jonathan Gillespie
+Copyright (c) 2018 Jonathan Gillespie
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -1,8 +1,9 @@
 # Nebula Framework for Salesforce Apex
-[![Deploy to Salesforce](https://img.shields.io/badge/salesforce-deploy-blue.svg)](https://githubsfdeploy.herokuapp.com)
-[![License: MIT](https://img.shields.io/badge/license-MIT-d742f4.svg)](https://opensource.org/licenses/MIT)
 [![Travis CI](https://img.shields.io/travis/jongpie/NebulaFramework/master.svg)](https://travis-ci.org/jongpie/NebulaFramework)
-[![Code Climate](https://img.shields.io/codeclimate/github/jongpie/NebulaFramework.svg)](https://codeclimate.com/github/jongpie/NebulaFramework)
+
+<a href="https://githubsfdeploy.herokuapp.com" target="_blank">
+    <img alt="Deploy to Salesforce" src="https://raw.githubusercontent.com/afawcett/githubsfdeploy/master/deploy.png">
+</a>
 
 Nebula is a development framework for Salesforce's Apex language on the Force.com platform. It aims to...
 1. Provide a foundation for Apex development, with the flexibility to be easily adapted to meet your implementation needs
@@ -11,14 +12,14 @@ Nebula is a development framework for Salesforce's Apex language on the Force.co
 4. Overcome some gaps in Apex and the Force.com platform
 
 ## Features
-Nebula focusses on streamlining how you work with SObjects
-1. **SObjectRepository.cls** - this module handles all DML actions & querying needs for an SObject, making the implementation of SObjects much easier & faster
-    * **QueryBuilder.cls** powers Nebula's querying, allowing you to dynamically build reusable SOQL & SOSL queries
-    * **SObjectRepositoryMock.cls** can be used in unit tests for test-driven development (TDD) & to drastically reduce the time of your unit tests.
-2. **SObjectTriggerHandler.cls** - this module provides a trigger framework to handle all trigger contexts provided by Salesforce, along with additional features like recursion prevention
+Nebula focusses on streamlining how you work with Sobjects
+1. **SobjectTriggerHandler.cls** - provides a trigger framework to handle all trigger contexts provided by Salesforce, along with additional features like recursion prevention
+2. **SobjectRepository.cls** - handles all DML actions & querying needs for an Sobject, making the implementation of Sobjects much easier & faster
+    * **Soql.cls and Sosl.cls** powers Nebula's querying & searching, allowing you to dynamically build reusable SOQL & SOSL queries
+    * **SobjectRepositoryMock.cls** can be used in unit tests for test-driven development (TDD) & to drastically reduce the time of your unit tests.
 
 The framework also provides several additional classes to make development easier
-1. **SObjectRecordTypes.cls** - record types are an important feature of the Force.com platform. Unfortunately, Apex has limitations with handling them - record types have a field called DeveloperName that (you guessed it!) should be used by developers... but native Apex describe methods cannot access this field. Nebula tries to overcome this by providing cacheable query results of record types so you can access the DeveloperName.
+1. **SobjectRecordTypes.cls** - record types are an important feature of the Force.com platform. Unfortunately, Apex has limitations with handling them - record types have a field called DeveloperName that (you guessed it!) should be used by developers... but native Apex describe methods cannot access this field. Nebula tries to overcome this by providing cacheable query results of record types so you can access the DeveloperName.
 2. **Logger.cls** - a flexible logging solution for Apex, leveraged by the framework itself
 3. **Environment.cls** - provides information about the current Salesforce environment
 4. **UUID.cls** - used to reate a randomly-generated unique ID in your code, using the Universally Unique Identifier (UUID) standard
@@ -34,7 +35,7 @@ Nebula also leverages custom settings to give you control over how the framework
     * Select if you want to include managed record types
 3. **Repository Settings (API Name: NebulaRepositorySettings__c)**
     * Automatically include common fields in your queries, like record ID, audit fields (CreatedById, CreatedDate, etc), Name field (or Subject field, where applicable) and more
-4. **Trigger Handler Settings (API Name: NebulaTriggerHandlerSettings__c)**   
+4. **Trigger Handler Settings (API Name: NebulaTriggerHandlerSettings__c)**
     * Easily disable all triggers & handlers (great for data migration and other admin tasks),
     * Enable or disable recursion prevention
 

src/aura/logger/logger.cmp

@@ -0,0 +1,26 @@
+<aura:component controller="Logger">
+
+    <!-- Private Attributes -->
+    <aura:attribute name="logEntries" type="LightningLogEntry[]" access="private" />
+
+    <!-- Public Functions -->
+    <aura:method name="addDebugEntry" action="{!c.addDebugEntry}">
+        <aura:attribute name="component" type="Object" required="true" />
+        <aura:attribute name="loggingLevelName" type="String" />
+        <aura:attribute name="message" type="String" />
+        <aura:attribute name="originLocation" type="String" required="true" />
+        <aura:attribute name="topics" type="String[]" />
+        <aura:attribute name="callback" type="function" />
+    </aura:method>
+
+    <aura:method name="addExceptionEntry" action="{!c.addExceptionEntry}">
+        <aura:attribute name="component" type="Object" required="true" />
+        <aura:attribute name="error" type="Error" />
+        <aura:attribute name="originLocation" type="String" required="true" />
+        <aura:attribute name="topics" type="String[]" />
+        <aura:attribute name="callback" type="function" />
+    </aura:method>
+
+    <aura:method name="save" action="{!c.save}" />
+
+</aura:component>

src/aura/logger/logger.cmp-meta.xml

@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<AuraDefinitionBundle xmlns="http://soap.sforce.com/2006/04/metadata">
+    <apiVersion>43.0</apiVersion>
+    <description>Logger for Lightning</description>
+</AuraDefinitionBundle>

src/aura/logger/loggerController.js

@@ -0,0 +1,11 @@
+({
+    addDebugEntry : function(component, event, helper) {
+        helper.addEntry(component, event);
+    },
+    addExceptionEntry : function(component, event, helper) {
+        helper.addEntry(component, event);
+    },
+    save : function(component, event, helper) {
+        helper.save(component, event);
+    }
+})

src/aura/logger/loggerHelper.js

@@ -0,0 +1,51 @@
+({
+    addEntry : function(component, event) {
+        var timestamp = new Date().toISOString();
+
+        var logEntries = component.get('v.logEntries');
+        if(logEntries == undefined || logEntries == null) logEntries = [];
+        var args = event.getParam('arguments');
+
+        var error;
+        if(args.error && args.error.message) {
+            error = {
+                columnNumber:  args.error.columnNumber,
+                lineNumber:    args.error.lineNumber,
+                message:       args.error.message,
+                stack:         args.error.stack
+            };
+        }
+
+        var logEntry = {
+            componentName:    args.component.getName(),
+            message:          args.message,
+            error:            error,
+            loggingLevelName: args.loggingLevelName,
+            originLocation:   args.originLocation,
+            topics:           args.topics,
+            timestamp:        timestamp
+        };
+        console.log('New Log Entry Added');
+        console.log(logEntry);
+        logEntries.push(logEntry);
+        component.set('v.logEntries', logEntries);
+    },
+    save : function(component, event) {
+        var logEntries = component.get('v.logEntries');
+
+        if(logEntries.size == 0) return;
+
+        var action = component.get('c.saveLightningEntries');
+        action.setParams({
+            logEntriesJson : JSON.stringify(logEntries)
+        });
+        action.setCallback(this, function(response) {
+            if(response.getState() === 'SUCCESS') {
+                component.set('v.logEntries', []);
+            } else if(response.getState() === 'ERROR') {
+                // TODO this.processCallbackErrors(response);
+            }
+        });
+        $A.enqueueAction(action);
+    }
+})