Added notification banner to docs

pkg/yqlib/doc/usage/convert.md

@@ -4,6 +4,12 @@ Encode and decode to and from JSON. Note that YAML is a _superset_ of JSON - so
 
 This means you don't need to 'convert' a JSON file to YAML - however if you want idiomatic YAML styling, then you can use the `-P/--prettyPrint` flag, see examples below.
 
+{% hint style="warning" %}
+Note that versions prior to 4.18 require the 'eval/e' command to be specified. 
+
+`yq e <exp> <file>`
+{% endhint %}
+
 ## Parse json: simple
 JSON is a subset of yaml, so all you need to do is prettify the output
 

pkg/yqlib/doc/usage/properties.md

@@ -4,6 +4,12 @@ Encode to a property file (decode not yet supported). Line comments on value nod
 
 By default, empty maps and arrays are not encoded - see below for an example on how to encode a value for these.
 
+{% hint style="warning" %}
+Note that versions prior to 4.18 require the 'eval/e' command to be specified. 
+
+`yq e <exp> <file>`
+{% endhint %}
+
 ## Encode properties
 Note that empty arrays and maps are not encoded by default.
 

pkg/yqlib/doc/usage/xml.md

@@ -6,6 +6,12 @@ Consecutive xml nodes with the same name are assumed to be arrays.
 
 XML content data and attributes are created as fields. This can be controlled by the `'--xml-attribute-prefix` and `--xml-content-name` flags - see below for examples.
 
+{% hint style="warning" %}
+Note that versions prior to 4.18 require the 'eval/e' command to be specified. 
+
+`yq e <exp> <file>`
+{% endhint %}
+
 ## Parse xml: simple
 Notice how all the values are strings, see the next example on how you can fix that.