New “Private” field support for passwords, application IDs and more

Four nice changes to Pipes this week.

First, ever wanted to share your Pipe but not your username, password or application ID? Now you can! Pipes now supports “private” fields in two new modules, the private input module and the private string module. Private fields are not visible to anyone but the Pipe creator, and are not copied if the Pipe is cloned. If a Pipe user doesn’t provide a value for a private input field, then any “default” value provided by the Pipe creator continues to be used – so your Pipes will run for anyone but only you can see the private values.

privateinput.jpg privatestring.jpg

Secondly, in addition to the new private modules we’ve added a “source” view for HTML formatted data in the editor’s debugger. So now those filters and regexes get a lot easier to write when you can easily browse the source directly:

html.jpg

source.jpg
Thirdly, we’ve enabled direct editing for the field selection drop down controls in the editor. This doesn’t sounds like a big deal until you realize you can now add array offsets to dig down into sub-arrays in the data, in any module (not just regex), or work on fields that aren’t currently flowing through the Pipe. For example, want to get at the first link in your raw ATOM feed? Rather than referring to the field as item.link.href, just type item.link.0.href
array.jpg

Finally, the Google feed issues we started experiencing last week should now be thing of the past. No more captchas. Yay!

This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>