inakianduaga / angular-remote-logger Goto Github PK

After #17 is implemented, we want to add a filter to censor out certain fields, which can be user defined, such as cc numbers and other financial information for example

Filter should allow for

{
"fieldName" : "type" 
}

where  `type` is remove|censor

We need to have the jasmine.clock.mockDate() function available, which is not on the current karma-jasmine version

We need to separate the actual decorator registration logic with the actual code itself, maybe using require.js as a dependency

Update: for good ideas,
http://solutionoptimist.com/2013/10/07/enhance-angularjs-logging-using-decorators/

• Use gulp-bump, gulp tag and gulp-git (also see gulp-release-tasks) to build a gulp release task that will bump package version, build the application for production, tag the release and push it to git master branch.
  • Since we are pushing directly to master without using a pull request, Travis shouldn't retrigger a build

• Convert all js to ts, add gulp tasks for build, add extra typings
• Use typescript classes for modules, etc

We want to be able to transform the logged payload in a certain way, for example strip CC numbers automatically. We need a way to register these filters and run them on the payload object

We want to be able to append to each payload certain fields, like datetime, or user id, or whatever. For this we need a way to register additional fields in each of the fields, which will extend the logged payload object

We need an "enabled" configuration variable that is true by default for both loggers. That way they can be dynamically disabled.

• Add a check for the flag in the code, if it's disabled it should do nothing, except return back the chain
• Update mock configuration/readme with examples
• Add tests for the disable case to make sure nothing is happening when disabled. Also add tests to dynamically toggle and make sure it works after reenabled.

• Travis (set up travis build)
• Coveralls
• Code climate

http://docs.travis-ci.com/user/languages/javascript-with-nodejs/
http://docs.travis-ci.com/user/build-configuration/

• Setup basic build
• Setup release when pushing to master
• Setup unit tests

• Instead of using console.log, use $log service
• Update tests

We need to remove the mocked dashboard variable and mock the constant (if possible), using provider , or otherwise just actually defining the constant, and removing the constant from the actual base code (or check to see if constant can be modified after the fact and code pays attention to it)

Update: We can first try by simply redefining the constant for the module using

module('angular-remote-logger')
  .constant('EXCEPTION_LOGGER_CONFIG', {NEW_OBJECT_WITH_VALUES})

which would be what a regular user would do for configuring the module