nested

Why does re-opening a nested module give different results depending on the syntax used? For example, this works fine: module A module E end end module A module E def E.e end end end But this: module A module E end end module A::E def E.e end end gives the error: reopen.rb:6:in `<module:E>': uninitialized constant A::E::E (NameError) from reopen.rb:5:in `<main>' (Before someone points this out, a workaround is to use self instead of the module name when defining E.e, but that's not really the point of this post.) The module keyword sets a namespace context that is checked for references to

I'm fairly new to using JSON (as opposed to XML) and am currently working purely with Javascript to digest, parse and display my returned JSON data. I'm using the JSON2.js library and am getting back some valid JSON data representing a fairly simple nested list: { "node":{ "class":"folder", "title":"Test Framework", "node":{ "class":"folder", "title":"Item 1", "node":{ "class":"folder", "title":"Item 1.1", "node":{ "class":"file", "title":"Item 1.1.a" } }, "node":{ "class":"folder", "title":"Item 1.2", "node":{ "class":"file", "title":"Item 1.2.a" }, "node":{ "class":"file", "title":"Item 1.2

I found that there are many if-else statements, especially nested if else statements, these statements make my code less readable. How to reduce the number of if else statements in PHP? My tips are as follows: 1.Use a switch statement when it is suitable; 2.use exit() statement when it is feasible; 3. Use ternary statement when it is feasible; Are there other tips that can reduce if else statements, especially nested if-else statements? Refactor your code into smaller work units. Too much conditional logic is a code-smell and usually indicates that your function needs to be refactored. Try to

I am using Ruby 1.9.2 and the Ruby on Rails v3.2.2 gem. I would like to "nest" the inclusion of modules given I am using the RoR ActiveSupport::Concern feature, but I have a doubt where I should state the include method. That is, I have the following: module MyModuleA extend ActiveSupport::Concern # include MyModuleB included do # include MyModuleB end end Should I state include MyModuleB in the "body" / "context" / "scope" of MyModuleA or I should state that in the included do ... end block? What is the difference and what I should expect from that? If you include MyModuleB in the "body" of

I have a document stored in ElasticSearch as below. _source: { "firstname": "John", "lastname": "Smith", "medals":[ { "bucket": 100, "count": 1 }, { "bucket": 150, "count": 2 } ] } I can access the string type value inside a document using doc.firstname for scripted metric aggregation http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-aggregations-metrics-scripted-metric-aggregation.html . But I am not able to get the field value using doc.medals[0].bucket. Can you please help me out and let me know how to access the values inside nested fields? Use _source for nested

I have a dynamodb table with an attribute containing a nested map and I would like to update a specific inventory item that is filtered via a filter expression that results in a single item from this map. How to write an update expression to update the location to "in place three" of he item with name=opel,tags include "x1" (and possibly also f3)? This should just update the first list elements location attribute. ( "inventory": [ { "location": "in place one", # I want to update this "name": "opel", "tags": [ "x1", "f3" ] }, { "location": "in place two", "name": "abc", "tags": [ "a3", "f5" ] }