<commit_before>[[TODO]]
----

 General things that I'd like to see or consider in the project.

 * Integration
   * Should have a configurable path that plugins can be found in
     * These will be automatically loaded 
   * Improve the examples of using Nark with a service

 * Testing
   * Cover the actual code that is created by the DSL
   * What happens when a user defines a method that accesses a variables they don't own?
    * Probably nothing
   * Make it easier to debug new plugins
     * How much time has it added to requests 
     * How much memory is Nark and/or a plugin taking up?
   * Create cucumber lib to help build and test plugins
     * This can be done by stealing the cucumber and rspec tests I run to create my own plugins
     * Should include debugging steps to help with development issue
     * How much time does the plugin add to requests
     * When creating plugins or interfaces.
     * Steps to help output the plugin in ruby format
 
 * Middleware 
   * Detach a plugin from Nark whilst the middle ware is running

 * Reporting engine
   * Allows you to log/store the data retrieved from Nark
     * Syslog interface
     * System Bus (supports stomp and other common protocols, include TCP/IP)
     * Socket
     * HTTP
     * RPC (though this won't be my primary focus)

 * Usability
   * When trying to create a plugin with the same name as one already included
   * When a plugin variable or method is already in use
   * Let the user know how event hooks are available.

 * Plugins
   * Improve the way descriptions are handled<commit_msg>Update TODO<commit_after>[[TODO]]
----

 General things that I'd like to see or consider in the project.

 * Integration
   * Should have a configurable path that plugins can be found in
     * These will be automatically loaded 
   * Improve the examples of using Nark with a service

 * Testing
   * Cover the actual code that is created by the DSL
   * What happens when a user defines a method that accesses a variables they don't own?
    * Probably nothing
   * Make it easier to debug new plugins
     * How much time has it added to requests 
     * How much memory is Nark and/or a plugin taking up?
   * Create cucumber lib to help build and test plugins
     * This can be done by stealing the cucumber and rspec tests I run to create my own plugins
     * Should include debugging steps to help with development issue
     * How much time does the plugin add to requests
     * When creating plugins or interfaces.
     * Steps to help output the plugin in ruby format
 
 * Middleware 
   * Detach a plugin from Nark whilst the middle ware is running

 * Reporting engine
   * Make using reporters easier
   * Allows you to log/store the data retrieved from Nark
     * Syslog interface
     * System Bus (supports stomp and other common protocols, include TCP/IP)
     * Socket
     * HTTP
     * RPC (though this won't be my primary focus)

 * Usability
   * When trying to create a plugin with the same name as one already included
   * When a plugin variable or method is already in use
   * Let the user know how event hooks are available.

 * Plugins
   * Improve the way descriptions are handled
{'fraction_non_alphanumeric': 0.03722239599624648, 'fraction_numerical': 0.0, 'mean_word_length': 2.9287469287469285, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '838003', 'n_tokens_mistral': 827, 'n_tokens_neox': 766, 'n_words': 478}