Skip to content
This repository was archived by the owner on Oct 2, 2019. It is now read-only.

Commit 8f6fb0b

Browse files
author
Eduardo Fullea
committed
Merge pull request #63 from efullea/filters
Removing commented out filter descriptions. Closes #39 and #40
2 parents 3ac612b + 5406f45 commit 8f6fb0b

File tree

1 file changed

+0
-72
lines changed

1 file changed

+0
-72
lines changed

index.html

Lines changed: 0 additions & 72 deletions
Original file line numberDiff line numberDiff line change
@@ -1775,78 +1775,6 @@ <h2><a>FilterOptions</a> Dictionary</h2>
17751775
</dl>
17761776
</section>
17771777

1778-
<!--
1779-
<p class="issue">
1780-
It needs to be discussed whether to just allow using the above
1781-
messaging-specific MessagingFilter or otherwise to allow defining filters with
1782-
a generic syntax (as defined in the following sections) and reflect in this
1783-
specification on which attributes the implementation is required to filter in
1784-
an efficient manner (e.g. creating the corresponding indexes).
1785-
</p>
1786-
1787-
<!------------------------ Interface CompositeFilter ------------------------->
1788-
<!--section>
1789-
<h2><a>CompositeFilter</a> Interface</h2>
1790-
<p>The <a>CompositeFilter</a> interface represents a filter that is the result
1791-
of combining several filters with an operator ('and' / 'or').
1792-
<dl title="interface CompositeFilter : AbstractFilter"
1793-
class="idl">
1794-
<dt>attribute AbstractFilter[] filters</dt>
1795-
<dd>The different filters that are combined in the composite
1796-
filter.</dd>
1797-
1798-
<dt>attribute CompositeFilterOperator operator</dt>
1799-
<dd>Indicates the operator used to combined the different filters. It can
1800-
have the following possible values: 'and' and 'or'.</dd>
1801-
</dl>
1802-
</section>
1803-
1804-
1805-
<!------------------------ Interface AttributeFilter-------------------------->
1806-
<!--section>
1807-
<h2><a>AttributeFilter</a> Interface</h2>
1808-
<p>The <a>AttributeFilter</a> interface represents a filter of messages
1809-
based on the value of a specific attribute.
1810-
<dl title="interface AttributeFilter : AbstractFilter"
1811-
class="idl">
1812-
<dt>attribute DOMString filterBy</dt>
1813-
<dd>The attribute based on whose value the messages are filtered.</dd>
1814-
1815-
<dt>attribute AttributeFilterOperator operator</dt>
1816-
<dd>Indicates the operator applied on the attribute indicated in the
1817-
<code>filterBy</code> parameter to filter the messages. It can have the
1818-
following possible values: 'is', 'contains', 'startswith', 'endswith',
1819-
'exists'.</dd>
1820-
1821-
<dt>attribute any filterValue</dt>
1822-
<dd>The value with which the attribute indicated in the
1823-
<code>filterBy</code> parameter is compared to filter the messages.</dd>
1824-
</dl>
1825-
</section>
1826-
1827-
1828-
<!------------------------ Interface AttributeRangeFilter -------------------->
1829-
<!--section>
1830-
<h2><a>AttributeRangeFilter</a> Interface</h2>
1831-
<p>The <a>AttributeRangeFilter</a> interface represents a filter of messages
1832-
with the value of a specific attribute within a range of values.
1833-
<dl title="interface AttributeRangeFilter : AbstractFilter"
1834-
class="idl">
1835-
<dt>attribute DOMString filterBy</dt>
1836-
<dd>The attribute based on whose value the messages are filtered.</dd>
1837-
1838-
<dt>attribute any startValue</dt>
1839-
<dd>The minum value that the attribute indicated in the
1840-
<code>filterBy</code> parameter may have so that the corresponding message
1841-
is included in the result of this filter.</dd>
1842-
1843-
<dt>attribute any endValue</dt>
1844-
<dd>The maximum value that the attribute indicated in the
1845-
<code>filterBy</code> parameter may have so that the corresponding message
1846-
si included in the result of this filter.</dd>
1847-
</dl>
1848-
</section>
1849-
18501778
<!------------------------ Interface Enumerations ---------------------------->
18511779
<section>
18521780
<h2>Enumerations</h2>

0 commit comments

Comments
 (0)