products forums blog support careers about
  History | Log In     View a printable version of the current page.  
PRO USERS, to ensure 'PRIORITY SUPPORT' make sure that your ASAP account is "tagged" when you file the request. Click here for instructions on how to tag your account.
Issue Details (XML | Word | Printable)

Key: ROR-1091
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Unprioritized Unprioritized
Assignee: Chris Williams
Reporter: Shalon Wood
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Aptana RadRails

Bogus 'Duplicate Hash Key: "null"' warnings

Created: 29/Dec/08 04:11 PM   Updated: 10/Mar/09 12:26 PM
Return to search
Component/s: Problems / Warnings
Affects Version/s: 1.1.0
Fix Version/s: 1.1.1

Impact on Workflow: Major
Studio Install Type: N/A
Participants: Chris Williams and Shalon Wood


 Description  « Hide
I've just imported my project into aptana (plugin version, on the latest version of Eclipse), and there are a ton of these warnings:
Duplicate hash key definition: 'null'

Here's a sample of the code in question:

Code:

<%= error_messages_for 'paragraphs' %> 

<!--[form:paragraphs]--> 
<p><label for="paragraphs_body">Body</label><br/> 
<%= text_area 'paragraphs', 'body_raw', "rows" => 10, "cols" => 80 %></p> 


<!--[eoform:paragraphs]-->

"cols" is highlighted when I go there from the line in the problem view. It appears, in fact, that any time there is more than one '=>' on a logical line, every key except the first will trigger that error.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Change by Chris Williams - 29/Dec/08 04:11 PM
Field Original Value New Value
Reporter Chris Williams [ cwilliams ] Shalon Wood [ dstar ]

Chris Williams - 29/Dec/08 04:13 PM
Fixed in 1.1 maintenance branch. Targeted for a 1.1.1 release. Will be merged into trunk for a 1.2.0 release.

Change by Chris Williams - 29/Dec/08 04:13 PM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Fix Version/s 1.1.1 [ 10150 ]

Chris Williams - 30/Dec/08 03:38 PM
Make sure all bugs marked fixed for 1.1.1 are also marked as fixed for 1.2.0 as the branch bugfixes have now been merged over to trunk.

Change by Chris Williams - 30/Dec/08 03:38 PM
Fix Version/s 1.2.0 [ 10082 ]

Chris Williams - 10/Mar/09 12:01 PM
Only tie things resolved in 1.1.2 and 1.2.0 to 1.1.2 as fixed version (since it's assumed that 1.2.0 as a later release will contain all the previous release's bugfixes).

Change by Chris Williams - 10/Mar/09 12:01 PM
Fix Version/s 1.1.2 [ 10153 ]
Fix Version/s 1.1.1 [ 10150 ]
Fix Version/s 1.2.0 [ 10082 ]

Change by Chris Williams - 10/Mar/09 12:26 PM
Fix Version/s 1.1.1 [ 10150 ]
Fix Version/s 1.1.2 [ 10153 ]