1
0
mirror of https://github.com/node-red/node-red.git synced 2023-10-10 13:36:53 +02:00

Merge pull request #1617 from node-red-hitachi/fix-backquote-in-info

Fix backquote in info text
This commit is contained in:
Nick O'Leary 2018-02-13 23:43:56 +00:00 committed by GitHub
commit 7f0174e6db
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 6 additions and 6 deletions

View File

@ -179,7 +179,7 @@
<dt>payload <span class="property-type">number</span></dt> <dt>payload <span class="property-type">number</span></dt>
<dd>the payload will be a 1 or a 0.</dd> <dd>the payload will be a 1 or a 0.</dd>
<dt>topic <span class="property-type">string</span></dt> <dt>topic <span class="property-type">string</span></dt>
<dd>the topic will be set to `pi/{the pin number}`.</dd> <dd>the topic will be set to <code>pi/{the pin number}</code>.</dd>
</dl> </dl>
<h3>Details</h3> <h3>Details</h3>
<p>You may also enable the input pullup resistor or the pulldown resistor.</p> <p>You may also enable the input pullup resistor or the pulldown resistor.</p>

View File

@ -75,7 +75,7 @@
<p>The node will listen on the configured path for requests of a particular type. <p>The node will listen on the configured path for requests of a particular type.
The path can be fully specified, such as <code>/user</code>, or include The path can be fully specified, such as <code>/user</code>, or include
named parameters that accept any value, such as <code>/user/:name</code>. named parameters that accept any value, such as <code>/user/:name</code>.
When named parameters are used, their actual value in a request can be accessed under `msg.req.params`.</p> When named parameters are used, their actual value in a request can be accessed under <code>msg.req.params</code>.</p>
<p>For requests that include a body, such as a POST or PUT, the contents of <p>For requests that include a body, such as a POST or PUT, the contents of
the request is made available as <code>msg.payload</code>.</p> the request is made available as <code>msg.payload</code>.</p>
<p>If the content type of the request can be determined, the body will be parsed to <p>If the content type of the request can be determined, the body will be parsed to

View File

@ -117,7 +117,7 @@
the response headers. The next node will then use those headers for its request - this the response headers. The next node will then use those headers for its request - this
is not usually the right thing to do. If <code>msg.headers</code> property is left unchanged is not usually the right thing to do. If <code>msg.headers</code> property is left unchanged
between nodes, it will be ignored by the second node. To set custom headers, <code>msg.headers</code> between nodes, it will be ignored by the second node. To set custom headers, <code>msg.headers</code>
should first be deleted or reset to an empty object: `{}`. should first be deleted or reset to an empty object: <code>{}</code>.
<h4>Cookie handling</h4> <h4>Cookie handling</h4>
<p>The <code>cookies</code> property passed to the node must be an object of name/value pairs. <p>The <code>cookies</code> property passed to the node must be an object of name/value pairs.
The value can be either a string to set the value of the cookie or it can be an The value can be either a string to set the value of the cookie or it can be an

View File

@ -65,7 +65,7 @@
that are part of a sequence.</p> that are part of a sequence.</p>
<p>The <b>recreate message sequences</b> option can be enabled to generate new message sequences <p>The <b>recreate message sequences</b> option can be enabled to generate new message sequences
for each rule that matches. In this mode, the node will buffer the entire incoming for each rule that matches. In this mode, the node will buffer the entire incoming
sequence before sending the new sequences on. The runtime setting `nodeMessageBufferMaxLength` sequence before sending the new sequences on. The runtime setting <code>nodeMessageBufferMaxLength</code>
can be used to limit how many messages nodes will buffer.</p> can be used to limit how many messages nodes will buffer.</p>
</script> </script>

View File

@ -337,7 +337,7 @@
</p> </p>
<h4>Storing messages</h4> <h4>Storing messages</h4>
<p>This node will buffer messages internally in order to work across sequences. The <p>This node will buffer messages internally in order to work across sequences. The
runtime setting `nodeMessageBufferMaxLength` can be used to limit how many messages nodes runtime setting <code>nodeMessageBufferMaxLength</code> can be used to limit how many messages nodes
will buffer.</p> will buffer.</p>
</script> </script>

View File

@ -90,7 +90,7 @@
</dl> </dl>
<h4>Storing messages</h4> <h4>Storing messages</h4>
<p>This node will buffer messages internally in order to work across sequences. The <p>This node will buffer messages internally in order to work across sequences. The
runtime setting `nodeMessageBufferMaxLength` can be used to limit how many messages nodes runtime setting <code>nodeMessageBufferMaxLength</code> can be used to limit how many messages nodes
will buffer.</p> will buffer.</p>
</script> </script>