@sitevision/api 1.1.0-alpha.2 → 2.0.0-alpha.1

package/server/PropertyUtil/index.js

@@ -5,74 +5,28 @@ Object.defineProperty(exports, "__esModule", {
 });
 exports["default"] = void 0;
 var _default = {
-  getBinary: function getBinary() {
-    return {};
-  },
-  getBoolean: function getBoolean() {
-    return true;
-  },
-  getCalendar: function getCalendar() {
-    return {};
-  },
-  getDouble: function getDouble() {
-    return 3.14;
-  },
-  getEnabledNode: function getEnabledNode() {
-    return {};
-  },
-  getEnabledString: function getEnabledString() {
-    return '';
-  },
-  getEnabledStringEscaped: function getEnabledStringEscaped() {
-    return '';
-  },
-  getInt: function getInt() {
-    return 3;
-  },
-  getNestedBinary: function getNestedBinary() {
-    return {};
-  },
-  getNestedBoolean: function getNestedBoolean() {
-    return true;
-  },
-  getNestedCalendar: function getNestedCalendar() {
-    return {};
-  },
-  getNestedDouble: function getNestedDouble() {
-    return 3.14;
-  },
-  getNestedInt: function getNestedInt() {
-    return 1;
-  },
-  getNestedNode: function getNestedNode() {
-    return {};
-  },
-  getNestedString: function getNestedString() {
-    return '';
-  },
-  getNestedStringEscaped: function getNestedStringEscaped() {
-    return '';
-  },
-  getNestedStrings: function getNestedStrings() {
-    return [''];
-  },
-  getNestedStringsEscaped: function getNestedStringsEscaped() {
-    return [''];
-  },
-  getNode: function getNode() {
-    return {};
-  },
-  getString: function getString() {
-    return '';
-  },
-  getStringEscaped: function getStringEscaped() {
-    return '';
-  },
-  getStrings: function getStrings() {
-    return [''];
-  },
-  getStringsEscaped: function getStringsEscaped() {
-    return [''];
-  }
+  getNestedString: function getNestedString() {},
+  getNestedStringEscaped: function getNestedStringEscaped() {},
+  getNestedInt: function getNestedInt() {},
+  getNestedDouble: function getNestedDouble() {},
+  getNestedBoolean: function getNestedBoolean() {},
+  getNestedNode: function getNestedNode() {},
+  getBinary: function getBinary() {},
+  getNestedBinary: function getNestedBinary() {},
+  getString: function getString() {},
+  getStringEscaped: function getStringEscaped() {},
+  getInt: function getInt() {},
+  getDouble: function getDouble() {},
+  getBoolean: function getBoolean() {},
+  getNode: function getNode() {},
+  getEnabledNode: function getEnabledNode() {},
+  getEnabledString: function getEnabledString() {},
+  getEnabledStringEscaped: function getEnabledStringEscaped() {},
+  getCalendar: function getCalendar() {},
+  getNestedCalendar: function getNestedCalendar() {},
+  getStrings: function getStrings() {},
+  getStringsEscaped: function getStringsEscaped() {},
+  getNestedStrings: function getNestedStrings() {},
+  getNestedStringsEscaped: function getNestedStringsEscaped() {}
 };
 exports["default"] = _default;

package/server/PublishingUtil/index.d.ts

@@ -1,4 +1,4 @@
-import Node from "../../hidden/javax/jcr/Node";
+import type { Node } from "../../types/javax/jcr/Node";
 
 /**
  * <p>
@@ -257,150 +257,12 @@ export function unpublishNode(aNode: Node, aDate: unknown): void;
  *    An instance of the Sitevision class implementing this interface can be obtained via
  *    {@link senselogic.sitevision.api.Utils#getPublishingUtil()}.
  *    See {@link senselogic.sitevision.api.Utils} for how to obtain an instance of the <code>Utils</code> interface.
- * </p><p>
- *    Publishes a node.
- * </p>
- * <p>
- *    Valid nodes are <code>sv:sitePage</code>, <code>sv:page</code>, <code>sv:article</code>, <code>sv:collaborationGroupPage</code>,
- *    <code>sv:template</code> and <code>sv:link</code> <em>(must be a "page link", a stand-alone link in the page tree)</em>.
- *    If another node is specified an <code>IllegalArgumentException</code> is thrown.
- * </p>
- *
- * <p>
- *    If no node is specified a <code>NullPointerException</code> is thrown.
- * </p>
- *
- * <p>
- *    The current user must be authorized to publish nodes or a <code>ConstraintViolationException</code> will be thrown.
- * </p><p>
- *    Schedules a node publish job for execution at a specified date.
- * </p>
- * <p>
- *    Valid nodes are <code>sv:sitePage</code>, <code>sv:page</code>, <code>sv:article</code>, <code>sv:collaborationGroupPage</code>,
- *    <code>sv:template</code> and <code>sv:link</code> <em>(must be a "page link", a stand-alone link in the page tree)</em>.
- *    If another node is specified an <code>IllegalArgumentException</code> is thrown.
- * </p>
- *
- * <p>
- *    If no node is specified a <code>NullPointerException</code> is thrown.
- * </p>
- *
- * <p>
- *    The current user must be authorized to publish nodes or a <code>ConstraintViolationException</code> will be thrown.
- * </p><p>
- *    Schedules a node publish job for execution at a specified date and a node unpublish job for execution at another date.
- * </p>
- * <p>
- *    Valid nodes are <code>sv:sitePage</code>, <code>sv:page</code>, <code>sv:article</code>, <code>sv:collaborationGroupPage</code>,
- *    <code>sv:template</code> and <code>sv:link</code> <em>(must be a "page link", a stand-alone link in the page tree)</em>.
- *    If another node is specified an <code>IllegalArgumentException</code> is thrown.
- * </p>
- *
- * <p>
- *    If no node is specified a <code>NullPointerException</code> is thrown.
- * </p>
- *
- * <p>
- *    The current user must be authorized to publish nodes or a <code>ConstraintViolationException</code> will be thrown.
- * </p><p>
- *    Publishes a node instantly with a best before notification date.
- * </p>
- * <p>
- *    Valid nodes are <code>sv:sitePage</code>, <code>sv:page</code>, <code>sv:article</code>, <code>sv:collaborationGroupPage</code>,
- *    <code>sv:template</code> and <code>sv:link</code> <em>(must be a "page link", a stand-alone link in the page tree)</em>.
- *    If another node is specified an <code>IllegalArgumentException</code> is thrown.
- * </p>
- *
- * <p>
- *    If a <code>aNotificationDate</code> is before current date a notification will be sent instantly.
- *    If <code>aNotificationDate</code> is null, no notification will be sent.
- * </p>
- *
- * <p>
- *    The current user must be authorized to publish nodes or a <code>ConstraintViolationException</code> will be thrown.
- * </p><p>
- *    Schedules a node publish job for execution at a specified date with a best before notification date.
- * </p>
- * <p>
- *    Valid nodes are <code>sv:sitePage</code>, <code>sv:page</code>, <code>sv:article</code>, <code>sv:collaborationGroupPage</code>,
- *    <code>sv:template</code> and <code>sv:link</code> <em>(must be a "page link", a stand-alone link in the page tree)</em>.
- *    If another node is specified an <code>IllegalArgumentException</code> is thrown.
- * </p>
- * <p>
- *    If <code>aNotificationDate</code> is null no notification will be sent. If <code>aNotificationDate</code>
- *    is before <code>aPublishDate</code> no notification will be sent since node hasn't been published yet.
- *    If a <code>aNotificationDate</code> is before current date, a notification will be sent instantly.
- * </p>
- *
- * <p>
- *    If <code>aPublishDate</code> is <code>null</code> or before current time, the node will be published instantly.
- * </p>
- *
- * <p>
- *    The current user must be authorized to publish nodes or a <code>ConstraintViolationException</code> will be thrown.
- * </p><p>
- *    Schedules a node publish job for execution at a specified date and a node unpublish job for execution at a later
- *    date and a best before notification date.
- * </p>
- * <p>
- *    Valid nodes are <code>sv:sitePage</code>, <code>sv:page</code>, <code>sv:article</code>, <code>sv:collaborationGroupPage</code>,
- *    <code>sv:template</code> and <code>sv:link</code> <em>(must be a "page link", a stand-alone link in the page tree)</em>.
- *    If another node is specified an <code>IllegalArgumentException</code> is thrown.
- * </p>
- *
- * <p>
- *    If <code>aNotificationDate</code> is null, no notification will be sent. If <code>aNotificationDate</code> is
- *    before <code>aPublishDate</code> no notification will be sent since node hasn't been published yet. If a
- *    <code>aNotificationDate</code> is before current date, a notification will be sent instantly.
- * </p>
- *
- * <p>
- *    If <code>aPublishDate</code> is <code>null</code> or before current time, the node will be published instantly.
- * </p>
- *
- * <p>
- *    If <code>aUnpublishDate</code> is before <code>aPublishDate</code> the unpublish job will run but won't affect
- *    the publishing, i.e. the node will be published at the given publish date.
- * </p>
- *
- * <p>
- *    The current user must be authorized to publish nodes or a <code>ConstraintViolationException</code> will be thrown.
- * </p><p>
- *    Unpublishes a node.
- * </p>
- * <p>
- *    Valid nodes are <code>sv:sitePage</code>, <code>sv:page</code>, <code>sv:article</code>, <code>sv:collaborationGroupPage</code>,
- *    <code>sv:template</code> and <code>sv:link</code> <em>(must be a "page link", a stand-alone link in the page tree)</em>.
- *    If another node is specified an <code>IllegalArgumentException</code> is thrown.
- * </p>
- *
- * <p>
- *    If no node is specified a <code>NullPointerException</code> is thrown.
- * </p>
- *
- * <p>
- *    The current user must be authorized to publish nodes or a <code>ConstraintViolationException</code> will be thrown.
- * </p><p>
- *    Schedules a node unpublish job for execution at a specified date.
- * </p>
- * <p>
- *    Valid nodes are <code>sv:sitePage</code>, <code>sv:page</code>, <code>sv:article</code>, <code>sv:collaborationGroupPage</code>,
- *    <code>sv:template</code> and <code>sv:link</code> <em>(must be a "page link", a stand-alone link in the page tree)</em>.
- *    If another node is specified an <code>IllegalArgumentException</code> is thrown.
- * </p>
- *
- * <p>
- *    If no node is specified a <code>NullPointerException</code> is thrown.
- * </p>
- *
- * <p>
- *    The current user must be authorized to publish nodes or a <code>ConstraintViolationException</code> will be thrown.
  * </p>
  * @author Mikael Wikblom
  * @since Sitevision 2.6.1_04
  */
-declare namespace PublishingUtil {
+declare namespace publishingUtil {
   export { publishNode, publishNodeWithNotification, unpublishNode };
 }
 
-export default PublishingUtil;
+export default publishingUtil;

package/server/QueryStringUtil/index.d.ts

@@ -399,313 +399,6 @@ export function getDateAsString(aDate: unknown): string;
  *    {@link senselogic.sitevision.api.search.SearchFactory#getQueryStringUtil()}.
  *    See {@link senselogic.sitevision.api.search.SearchFactory} for how to obtain
  *    an instance of the <code>SearchFactory</code> interface.
- * </p>Strips all trailing "any" chars.
- *
- * <p>
- *    The question mark character is a query syntax char (the "any" char) and can potentially screw up querying
- *    <em>(i.e. the parser fails to parse the query or return unexpected result)</em>.
- *    This method removes all trailing "any" chars (i.e. removes all trailing question marks).
- * </p>
- *
- * <table style="border:1px solid black" summary="">
- *    <caption style="text-align:left">Some examples</caption>
- *    <tr>
- *       <th>aQueryString</th><th>Returned</th>
- *    </tr>
- *    <tr>
- *       <td><code>"when is halloween"</code></td><td><code>"when is halloween"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"when is halloween?"</code></td><td><code>"when is halloween"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"when is halloween??"</code></td><td><code>"when is halloween"</code></td>
- *    </tr>
- * </table>Strips Local params for a query string.
- *
- * <p>
- *    Local params are a query string prefix that starts with "<code>{!</code>" and ends with "<code>}</code>".
- *    The Local Params can override/sidestep or affect desired search behaviour. This method strips Local params to prohibit that.
- *    Leading whitespace of Local params will also be stripped.
- * </p>
- * <table style="border:1px solid black" summary="">
- *    <caption style="text-align:left">Some examples</caption>
- *    <tr>
- *       <th>aQueryString</th><th>Returned</th>
- *    </tr>
- *    <tr>
- *       <td><code>null</code></td><td><code>null</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>""</code></td><td><code>""</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"hello query"</code></td><td><code>"hello query"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"{!}"</code></td><td><code>""</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"{!}hey"</code></td><td><code>"hey"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"{!whatever}foo"</code></td><td><code>"foo"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"{!whatever} bar"</code></td><td><code>" bar"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>" {! whatever }baz"</code></td><td><code>"baz"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"{!whatever"</code></td><td><code>"{!whatever"</code></td>
- *    </tr>
- * </table>Removes all query syntax characters from a query string and trims the result.
- *
- * <p>
- *    Current query syntax characters are:<br>
- *    <code>+ - &amp;&amp; || ! ( ) { } [ ] ^ " ~ * ? : \</code><br>
- * </p>
- *
- * <p>
- *    <em>Note! This is a legacy shortcut for (strict/non-lenient)
- *    {@link #removeQuerySyntaxChars(String, boolean) removeQuerySyntaxChars(aQueryString, false)}.</em>
- * </p>Removes query syntax characters from a query string and trims the result.
- *
- * <p>
- *    Current query syntax characters are:<br>
- *    <code>+ - &amp;&amp; || ! ( ) { } [ ] ^ " ~ * ? : \</code><br>
- * </p>
- * <p>
- *    Processing:
- * </p>
- * <ul>
- *    <li>
- *       The "any" char will be removed, i.e: <code>"ma?nus" -&gt; "manus"</code>
- *    </li>
- *    <li>
- *       The "double" chars will be replaced with a "single" char, i.e: <code>"ma&amp;&amp;nus" -&gt; "ma&amp;nus"</code>
- *       and <code>"ma||nus" -&gt; "ma|nus"</code>
- *    </li>
- *    <li>
- *       The "not" chars will be removed, unless <code>aLenientRemove</code> is <code>true</code>. Lenient behaviour will
- *       try to keep all dashes that can be interpreted as "word separators" <em>("bindestreck" in swedish)</em>.
- *    </li>
- *    <li>
- *       Other chars will be replaced with a space. Subsequent syntax chars will only result in one space,
- *       e.g: <code>"This is *so* funny!" -&gt; "This is so funny"</code>
- *    </li>
- * </ul>
- *
- * <table style="border:1px solid black" summary="">
- *    <caption style="text-align:left">Some examples</caption>
- *    <tr>
- *       <th>aQueryString</th><th>aLenientRemove</th><th>Returned</th>
- *    </tr>
- *    <tr>
- *       <td><code>"(Site?vision: *Enterprise) !?"</code></td><td><code>true / false</code></td><td><code>"Sitevision Enterprise"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"Anna-Karin?"</code></td><td><code>true</code></td><td><code>"Anna-Karin"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"Anna-Karin?"</code></td><td><code>false</code></td><td><code>"Anna Karin"</code></td>
- *    </tr>
- * </table>Gets a prefix/wildcard query that potentially will be scored.
- *
- * <p>
- *    <em>The general purpose/advantage of a raw wildcard query (i.e Prefix query) is that it will result in hits also for a partial word.
- *    Typical a good thing for all "live-search/type-ahead" solutions.
- *    The downside is that the search result of such query can be a real mess since all wildcard-hits are scored exactly the same
- *    ("constant scoring"). In practice, this means that the hits of such search result can show up in random order.</em>
- * </p>
- * <p>
- *    This method returns a <em>"smart"</em> wildcard query that combines the <strong>prefix-matching advantage</strong> of a raw wildcard query
- *    with potential <strong>scoring capabilities</strong>.
- *    This is achieved by a expanding the word to multiple terms and adding the wildcard to one of them and use an implicit OR.
- *    In other words: <em>"build a query that matches the exact word or the wildcarded word"</em>.
- * </p>
- * <p>
- *    The query string <code>"Car"</code> transformed into a smart wildcard query <code>"+(Car car*)"</code>
- *    could conceptually result in a search result like this:
- * </p>
- * <ol>
- *    <li>"Car sales" <em>(exact clause match + wildcard clause match: score 1.23)</em></li>
- *    <li>"Carpets" <em>(wildcard clause match: constant scoring 1)</em></li>
- *    <li>"Careless" <em>(wildcard clause match: constant scoring 1)</em></li>
- * </ol>
- * <p>
- *    The word that is wildcarded will also be lowercased for better matching <em>(typically the query parser is primarily set up to use/query
- *    analyzed fields, i.e. typically lowercased)</em>.
- *    A word with a dash is potentially further duplicated for increased matching <em>(dash is the "any" syntax char but is handled lenient)</em>.
- *    A word that ends with a {@link #removeQuerySyntaxChars(String, boolean) syntax character} will typically not be wildcarded at all.
- *    A word that contains a syntax character will typically get a raw wildcard as-is.
- * </p>
- *
- * <table style="border:1px solid black" summary="">
- *    <caption style="text-align:left">Some examples</caption>
- *    <tr>
- *       <th>aQueryString</th><th>Returned</th>
- *    </tr>
- *    <tr>
- *       <td><code>null</code></td><td><code>null</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>" "</code></td><td><code>null</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"Car"</code></td><td><code>"+(Car car*)"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"Car*"</code></td><td><code>"+(Car car*)"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"Car?"</code></td><td><code>"Car?"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"title:Car"</code></td><td><code>"title:Car*"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"Anna-Carin"</code></td><td><code>"+(Anna-Carin AnnaCarin (+Anna +carin*) anna-carin* annacarin*)"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"019-173030"</code></td><td><code>"+(019-173030 019173030 (+019 +173030*) 019-173030* 019173030*)"</code></td>
- *    </tr>
- * </table>
- *
- * <p>
- *    The smart wildcard query <strong>downside/caveat</strong> is that the actual query is more complex. This increased complexity
- *    will typically distort the pattern matching for the Solr <em>Elevation</em> component, i.e. "elevated/sponsored" hits will typically
- *    never work for smart wildcard queries.
- * </p>Transforms a string with delimiters to a string that could be used in a field-grouped query expression.
- *
- * <p>
- *    This is a convenience method when you want to query something based on items in a string that are delimited
- *    by some token. A typical example is a "keyword" metadata that contains multiple keywords delimited by a comma char.
- * </p>
- *
- * <p>
- *    This method splits the <code>aStringToSplit</code> with the <code>aSplitExpression</code> and each part is
- *    then trimmed and appended to the resulting string, separated with a space. Parts that contains a space char
- *    is quoted.
- * </p>
- *
- * <table style="border:1px solid black" summary="">
- *    <caption style="text-align:left">Some examples</caption>
- *    <tr>
- *       <th style="text-align:left">aStringToSplit</th><th style="text-align:left">aSplitExpression</th><th style="text-align:left">Returned</th>
- *    </tr>
- *    <tr>
- *       <td><code>"one"</code></td><td><code>","</code></td><td><code>one</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"one,two"</code></td><td><code>","</code></td><td><code>one two</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"one, two"</code></td><td><code>","</code></td><td><code>one two</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"one, two, three four"</code></td><td><code>","</code></td><td><code>one two "three four"</code></td>
- *    </tr>
- *    <tr><td colspan="3">&nbsp;</td></tr>
- *    <tr>
- *       <td><code>"one"</code></td><td><code>"aNonMatchingExpression"</code></td><td><code>one</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"one,two"</code></td><td><code>"aNonMatchingExpression"</code></td><td><code>one,two</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"one, two"</code></td><td><code>"aNonMatchingExpression"</code></td><td><code>"one, two"</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"one, two, three four"</code></td><td><code>"aNonMatchingExpression"</code></td><td><code>"one, two, three four"</code></td>
- *    </tr>
- *    <tr><td colspan="3">&nbsp;</td></tr>
- *    <tr>
- *       <td><code>null</code></td><td><code>","</code></td><td><code>null</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>null</code></td><td><code>null</code></td><td><code>null</code></td>
- *    </tr>
- *    <tr><td colspan="3">&nbsp;</td></tr>
- *    <tr>
- *       <td><code>"one"</code></td><td><code>null</code></td><td><code>one</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"one,two"</code></td><td><code>null</code></td><td><code>one,two</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"one, two"</code></td><td><code>null</code></td><td><code>one, two</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>"one, two, three four"</code></td><td><code>null</code></td><td><code>one, two, three four</code></td>
- *    </tr>
- * </table>Transforms multiple strings with delimiters to a string that could be used in a field-grouped query expression.
- *
- * <p>
- *    This is a convenience method that executes {@link #splitToQueryParts(String, String)} for a collection of strings
- *    and appends each returned value to a combined result, separated with a space. Whitespace only or <code>null</code>
- *    values will be ignored.
- * </p>
- * <p>
- *    <em>See {@link #splitToQueryParts(String, String)} how each string of the collection will be transformed.</em>
- * </p>Returns a field query that is properly grouped.
- *
- * <p>
- *    This method trims the <code>aValueExpression</code> and analyzes the space-separated parts, quoted and unquoted.
- *    The result will be a grouped field query if there are multiple parts in <code>aValueExpression</code> and a
- *    non-grouped field query if there are only one part in <code>aValueExpression</code>.
- * </p>
- * <p>
- *    Note that this is a convenience method only. Neither field or value will be syntactically checked in any way.
- *    The caller of this method is responsible for passing values that the query parser used later on will accept.
- * </p>
- *
- * <table style="border:1px solid black" summary="">
- *    <caption style="text-align:left">Some examples</caption>
- *    <tr>
- *       <th style="text-align:left">aFieldName</th>
- *       <th style="text-align:left">aValueExpression</th>
- *       <th style="text-align:left">Returned</th>
- *    </tr>
- *    <tr>
- *       <td><code>content.analyzed</code></td>
- *       <td><code>sitevision</code></td>
- *       <td><code>content.analyzed:sitevision</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>+content.analyzed</code></td>
- *       <td><code>sitevision*</code></td>
- *       <td><code>+content.analyzed:sitevision*</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>-content.analyzed</code></td>
- *       <td><code>enterprise</code></td>
- *       <td><code>-content.analyzed:enterprise</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>content.analyzed</code></td>
- *       <td><code>"sitevision enterprise"</code></td>
- *       <td><code>content.analyzed:"sitevision enterprise"</code></td>
- *    </tr>
- *    <tr><td colspan="3">&nbsp;</td></tr>
- *    <tr>
- *       <td><code>content.analyzed</code></td>
- *       <td><code>sitevision enterprise</code></td>
- *       <td><code>content.analyzed:(sitevision enterprise)</code></td>
- *    </tr>
- *    <tr>
- *       <td><code>content.analyzed</code></td>
- *       <td><code>portal "sitevision enterprise"</code></td>
- *       <td><code>content.analyzed:(portal "sitevision enterprise")</code></td>
- *    </tr>
- * </table>Returns a date formatted according to the Solr date string representation.
- *
- * <p>
- *    All dates in Solr (Lucene) are stored using UTC (zulu time 'Z').
- *    When a date is converted to a string that should be sent to Solr
- *    (for example as a part of a query) the timezone must be taken into
- *    consideration since no adjustments will be performed by the query parser.
  * </p>The "match all" query string.
  *
  * <p>
@@ -720,8 +413,9 @@ export function getDateAsString(aDate: unknown): string;
  * </p>
  * @author Magnus Lövgren
  * @since Sitevision 3.6
+ * @since Sitevision 8.2
  */
-declare namespace QueryStringUtil {
+declare namespace queryStringUtil {
   export {
     stripTrailingAnyChars,
     stripLocalParams,
@@ -734,4 +428,4 @@ declare namespace QueryStringUtil {
   };
 }
 
-export default QueryStringUtil;
+export default queryStringUtil;

package/server/QueryStringUtil/index.js

@@ -0,0 +1,17 @@
+"use strict";
+
+Object.defineProperty(exports, "__esModule", {
+  value: true
+});
+exports["default"] = void 0;
+var _default = {
+  stripTrailingAnyChars: function stripTrailingAnyChars() {},
+  stripLocalParams: function stripLocalParams() {},
+  removeQuerySyntaxChars: function removeQuerySyntaxChars() {},
+  smartWildcard: function smartWildcard() {},
+  splitToQueryParts: function splitToQueryParts() {},
+  splitCollectionToQueryParts: function splitCollectionToQueryParts() {},
+  getFieldQuery: function getFieldQuery() {},
+  getDateAsString: function getDateAsString() {}
+};
+exports["default"] = _default;

package/server/RedirectUtil/index.d.ts

@@ -1,11 +1,11 @@
-import Node from "../../hidden/javax/jcr/Node";
+import type { Node } from "../../types/javax/jcr/Node";
 
 /**
  * Gets all 301 redirect URIs registered for a specific node.
  * @param aNode a node, typically a <code>sv:page</code>
  * @return a set of 301 redirect URIs for <code>aNode</code>, never <code>null</code>
  */
-export function getRedirectURIs(aNode: Node): Set<unknown>;
+export function getRedirectURIs(aNode: Node): unknown;
 
 /**
  * Adds a relative URI that should trigger a 301 redirect to a specific node.
@@ -65,27 +65,11 @@ export function removeAllRedirectURIs(aNode: Node): void;
  *    An instance of the Sitevision class implementing this interface can be obtained via
  *    {@link senselogic.sitevision.api.Utils#getRedirectUtil()}.
  *    See {@link senselogic.sitevision.api.Utils} for how to obtain an instance of the <code>Utils</code> interface.
- * </p>Gets all 301 redirect URIs registered for a specific node.Adds a relative URI that should trigger a 301 redirect to a specific node.
- *
- * <p>
- *    Permission note! Current user must have {@link senselogic.sitevision.api.security.PermissionUtil.Permission#WRITE} on <code>aNode</code>.
- * </p>Adds a collection of relative URIs that should trigger 301 redirects to a specific node.
- *
- * <p>
- *    Permission note! Current user must have {@link senselogic.sitevision.api.security.PermissionUtil.Permission#WRITE} on <code>aNode</code>.
- * </p>Removes a relative 301 redirect URI from a specific node.
- *
- * <p>
- *    Permission note! Current user must have {@link senselogic.sitevision.api.security.PermissionUtil.Permission#WRITE} on <code>aNode</code>.
- * </p>Removes all relative 301 redirect URIs from a specific node.
- *
- * <p>
- *    Permission note! Current user must have {@link senselogic.sitevision.api.security.PermissionUtil.Permission#WRITE} on <code>aNode</code>.
  * </p>
  * @author Magnus Lövgren
  * @since Sitevision 4.0.3
  */
-declare namespace RedirectUtil {
+declare namespace redirectUtil {
   export {
     getRedirectURIs,
     addRedirectURI,
@@ -95,4 +79,4 @@ declare namespace RedirectUtil {
   };
 }
 
-export default RedirectUtil;
+export default redirectUtil;