Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 58599 invoked from network); 14 Feb 2011 16:10:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Feb 2011 16:10:57 -0000 Received: (qmail 36466 invoked by uid 500); 14 Feb 2011 16:10:56 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 36276 invoked by uid 500); 14 Feb 2011 16:10:54 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 36256 invoked by uid 99); 14 Feb 2011 16:10:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Feb 2011 16:10:53 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [80.244.253.218] (HELO mail.traeumt.net) (80.244.253.218) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Feb 2011 16:10:45 +0000 Received: from dahlia.local (p5799EDCB.dip.t-dialin.net [87.153.237.203]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.traeumt.net (Postfix) with ESMTPSA id 58F6F3C2D0 for ; Mon, 14 Feb 2011 17:10:24 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1082) Subject: Re: Spaces in View Names From: Jan Lehnardt In-Reply-To: <4D594FD3.1010506@couchone.com> Date: Mon, 14 Feb 2011 17:10:23 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <7B12D18A-0392-4997-B705-AD61419B792D@apache.org> References: <4D594FD3.1010506@couchone.com> To: dev@couchdb.apache.org X-Mailer: Apple Mail (2.1082) Hi Benjamin, On 14 Feb 2011, at 16:52, Benjamin Young wrote: > Hi all, >=20 > It's currently possible to include space characters in View names, so = your map/reduce URL can (actually) look like this: > /db/_design/app/_view/ > (there are 5 spaces at the end of that partial "URL") >=20 > Encoded it would look like this: > /db/_design/app/_view/%20%20%20%20%20 >=20 > Needless to say this could be potentially quite confusing--though I = suppose we could consider it an obfuscation option. :/ >=20 > Should this be considered a "bug" and avoided in future views? or just = considered an option that one should be careful when using? >=20 > This came to my attention as Futon currently adds %20's to the names = when displayed in dropdowns. Futon2, however, doesn't currently do = that--making it nearly impossible to click the name of the view = above--it at least looks like a bug in the UI. >=20 > Additionally, when editing documents with a view named with all = spaces, the keys are displayed as un-viewable whitespace until you edit = that chunk. In Futon2 it's currently impossible to edit that piece of = the document (as you can't click it). >=20 > As I'm working on Futon2, I'm wanting to determine what's the best way = to handle spaces in view names. Should they be removed as an option for = that portion of the URL going forward? Should Futon2 escape them in any = visual reference to them (as Futon1 currently does in most cases)? >=20 > Just wanted to get some discussion on this before I picked a way = forward. :) Thanks for bringing this up. I think we should not allow spaces in view = names. Cheers Jan --=20