Skip to content
  1. Oct 15, 2013
  2. Oct 10, 2013
  3. Oct 09, 2013
  4. Oct 04, 2013
  5. Oct 02, 2013
  6. Sep 27, 2013
  7. Sep 26, 2013
  8. Sep 23, 2013
    • Rene Saarsoo's avatar
      Implement @experimental tag. · c373eadb
      Rene Saarsoo authored
      Placed it in the same group with @deprecated and @removed, so one
      can also add a version number (since when the feature was added),
      and a comment:
      
          @experimental 3.2 To try out new Google API.
      
      Tweaked the styles of @deprecated and @removed too, so they all look
      a bit better.  To allow for different message text in @experimental,
      had to introduce @msg and @since instance variables to the DeprecatedTag
      base class.
      
      Fixes #239
      c373eadb
  9. Sep 18, 2013
  10. Sep 17, 2013
    • Rene Saarsoo's avatar
      Create new Performance group of command line options. · 23c7e6b8
      Rene Saarsoo authored
      Grouping the --processes, --cache and --cache dir inside it.
      23c7e6b8
    • Rene Saarsoo's avatar
      Merge branch 'cache' · 05935c74
      Rene Saarsoo authored
      05935c74
    • Rene Saarsoo's avatar
      Additional documentation of caching. · 4f5fd72a
      Rene Saarsoo authored
      Refs #446
      4f5fd72a
    • Rene Saarsoo's avatar
      Invalidate cache generated by different Ruby/JSDuck version. · 0fc22515
      Rene Saarsoo authored
      Marshal dump format can change between Ruby versions and although
      the Marshal has its own version numbers, I get an encoding error
      when reading the Ruby 1.8 Marshal dump with Ruby 1.9.
      
      The parsed source code data structure can also change between
      versions of JSDuck.
      
      To eliminate these problems, a .cache/manifest.txt file is created
      with the contents like:
      
          Ruby: 1.9.3, JSDuck: 5.2.0
      
      The file is then checked to match the current version of Ruby and
      JSDuck.  If the versions don't match, the whole cache is invalidated
      (all files removed from it).
      
      Refs #446
      0fc22515
    • Rene Saarsoo's avatar
      Invalidate cache when files are renamed. · 4347e94a
      Rene Saarsoo authored
      Take the file name also into account when calculating the MD5 hash
      of a cache entry.  Otherwise files that are renamed would also be
      read from cache, resulting in the old filename being referenced in
      the docs and also in the warning messages.
      
      Refs #446
      4347e94a
    • Rene Saarsoo's avatar
      Clean up unused files from .cache directory. · 44e73fc8
      Rene Saarsoo authored
      We remember each cache entry that was read or written during the
      current jsduck run.  All others get deleted.  This ensures the .cache
      directory doesn't grow over time.
      
      Refs #446
      44e73fc8
    • Rene Saarsoo's avatar
      Add --[no-]cache and --cache-dir options. · 9a0f2263
      Rene Saarsoo authored
      By default the caching is disabled.  When turned on with --cache,
      the caching dir will be <output-dir>/.cache/ unless overridden
      with --cache-dir option.
      
      Previously the whole output dir got cleaned up, but now it can
      contain a .cache dir, which we'll want to preserve.  So I created
      OutputDir class to take care of output directory cleanup in a way
      that preserves the .cache/ directory inside it.
      
      Refs #446
      9a0f2263
    • Rene Saarsoo's avatar
      Improve --export option docs. · c099922b
      Rene Saarsoo authored
      Refs #450
      c099922b
  11. Sep 16, 2013
    • Rene Saarsoo's avatar
      Initial prototype of caching parsed source code. · 2bfd8b1f
      Rene Saarsoo authored
      At the moment the cache is just saved to .cache/ in current dir.
      
      The parsed data is serialized into binary format using Marshal,
      which correctly preserves all the data types and is additionally
      really fast.
      
      Refs #446
      2bfd8b1f
  12. Sep 13, 2013
  13. Sep 12, 2013