Issue Summary

Creating content property keys with dashes thru AP.confluence.setContentProperty() are saved as underscores thus accessing through CQL (content.property[my-content-property]) would fail.

Steps to Reproduce

1. Create a new content property key with dashes in the string (eg "my-content-property").
2. Use AP.confluence.setContentProperty() to insert a new content property value.
3. Get content and expand properties: /wiki/rest/api/content/ {id}

   ?expand=metadata.properties

4. You'll see that the key has been saved as "my_content_property".
5. Any attempt to access that content property using the original key name with dashes will fail (eg via CQL content.property[my-content-property]).

Expected Results

Properties are saved as is

Actual Results

Properties are converted from "-" to "_"

Notes

• Would be great if doco is updated to accomodate this behavior or don't convert dashes

  Workaround

• Replace "-" with "_" on CQL search