couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Venediger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (COUCHDB-191) Bad javascript syntax in Futon's custom query editor doesn't show an error when run.
Date Sun, 04 Jan 2009 13:45:44 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Luke Venediger resolved COUCHDB-191.
------------------------------------

       Resolution: Cannot Reproduce
    Fix Version/s: 0.9

I've just discovered that the page does in fact report the error, via a javascript alertbox.
It could probably be a bit more user-friendly, but I'll close this issue and open a new one
with a feature request.

> Bad javascript syntax in Futon's custom query editor doesn't show an error when run.

> -------------------------------------------------------------------------------------
>
>                 Key: COUCHDB-191
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-191
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Administration Console
>    Affects Versions: 0.9
>         Environment: OS: EEEubuntu (based on Ubuntu 8.10). Hardware: EEE PC 904hd. Browser:
Firefox 3.0.5. 
>            Reporter: Luke Venediger
>            Priority: Minor
>             Fix For: 0.9
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> In the custom view editor, Futon doesn't report an error when there is bad syntax in
the javascript. 
> To reproduce:
> 1. Browse to http://localhost:5984/_utils/
> 2. Open a database
> 3. Change the view to "Custom Query..."
> 4. In the view code section:
>     change: emit(null, doc);
>     to: emit(null, doc
> 5. Click "Run"
> Actual results:
> The page returns with an empty table below the query editor.
> Expected results:
> The page should return showing a message like "Error in view. Missing ')' after doc,
line 3"
> Notes:
> The http response was 200 OK, where it should've been a 400 - Bad Request.   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message