Code Monkey home page Code Monkey logo

jtrack's Introduction

jTrack

##Universal Tracking coming soon

jQuery plugin for Google Tracking. For a complete list of options and examples see the wiki.

CHANGELOG:

  • 1.3.0 (bootstrap 0.4.0) updates the bootstrap to match the WSU global data collection scheme

jtrack's People

Contributors

jeremyfelt avatar quantumjlbass avatar

Stargazers

 avatar Ross Dallaire avatar

Watchers

Dan White avatar James Cloos avatar Danial Bleile avatar Clint Young avatar  avatar Michelle Felt avatar Jon Bickelhaupt avatar Jeff Hanson avatar  avatar Courtney Chaffin avatar  avatar  avatar  avatar

Forkers

quantumjlbass

jtrack's Issues

Default eventValue is 1

I'm not sure if this is intentional or not, but the eventValue passed for events appears to default to 1 if not specified elsewhere. I haven't poked at it too much, but as an integer is expected, it seems like it should default to null rather than the value checked for here: https://github.com/washingtonstateuniversity/jTrack/blob/dev/jtrack.js#L184

In the meantime, I've updated the WSUWP analytics plugin to pass value: null for each event to make sure none is sent.

Tag next release of jTrack

I'd be in favor of tagging a new release this week. Does 1.2.6, 1.3.0, or something else make sense? The internal version number in the script appears to have been bumped a few times without a tagged release. I'm not sure which one is important. /cc @jeremyBass

Add options event

Just before the whole process is loaded, and each account is iterated through, there is need to be able to access the object and alter it. This will provide a way to set up details at the last sec when dealing with plugins. That short is that if I need to make an alteration in the way the data is handled, and the CMS is controlling the setup, I may run in to a wall where I can't do the option update with out updating the plugin it's self.

  • add an options event
  • set up on complete event
  • id any other events that may be helpful

Build Workflow Questions

Thoughts while scripting the deployment for this on repo.wsu.edu:

  • Any issues with using develop instead of dev as the development branch? This would align with Spine and help with the reuse of the bash scripts over time.
  • Can we remove the version number from the built files, similar to the Spine?
  • Can we remove all built files from the repository once they're available for production use on repo.wsu.edu?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.