Prep for 2.0 release (ver 1.9.0)

- Using versions 1.9.x for pre-2.0 releases.  Not sure if this is the right
  semantic versioning approach, but Splunkbase doesn't seem to like release
  candidate versions.  We'll keep this the non-default option on Splunkbase.
- Enabled the ksconf-sort pre-commit hook and ran it once against all files.

.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 1.0.1
+current_version = 1.9.0
 tag = True
 commit = True
 

.pre-commit-config.yaml

@@ -26,4 +26,4 @@ repos:
   sha: v0.5.3
   hooks:
     - id: ksconf-check
-#    - id: ksconf-sort
+    - id: ksconf-sort

default/app.conf

@@ -1,11 +1,11 @@
+[launcher]
+author = Lowell Alleman
+description = Implementation of JMESPath for splunk (xpath for json)
+version = 1.9.0
+
 [package]
 check_for_updates = 1
-id=jmespath
-
-[launcher]
-version = 1.0.1
-description=Implementation of JMESPath for splunk (xpath for json)
-author=Lowell Alleman
+id = jmespath
 
 [ui]
 is_visible = false

default/commands.conf

@@ -1,8 +1,8 @@
 [jmespath]
 filename = jpath.py
-streaming = true
-retainsevents = true
-overrides_timeorder = false
-supports_rawargs = true
 is_risky = false
+overrides_timeorder = false
+retainsevents = true
+streaming = true
 supports_multivalues = true
+supports_rawargs = true

default/searchbnf.conf

@@ -1,3 +1,5 @@
+# KSCONF-NO-SORT
+
 [jmespath-command]
 syntax = jmespath <jmespath-string> (field=<field>)? (outfield=<field>)? (default=<string>)?
 shortdesc = Declaratively specify how to extract elements from a JSON document using JMESPath