Skip to content

Fix issue when response contains a node with the same name as an existing class#1

Open
gonfva wants to merge 1 commit intotripit:masterfrom
gonfva:patch-2
Open

Fix issue when response contains a node with the same name as an existing class#1
gonfva wants to merge 1 commit intotripit:masterfrom
gonfva:patch-2

Conversation

@gonfva
Copy link

@gonfva gonfva commented Mar 12, 2014

If we receive a response like

<Response><timestamp>1394617345</timestamp><num_bytes>6625</num_bytes><Trip>....

and we have an existing class called Trip, the process could crash while trying to create the Trip object. The code in TravelObj#new tries to get and crate constants that belongs to a module, but it does it inheriting. This change just avoids inheriting, so that it looks only in the module.

If we receive a response like 

<Response><timestamp>1394617345</timestamp><num_bytes>6625</num_bytes><Trip>....

and we have an existing class called Trip, the process could crash while trying to create the Trip object. The code in TravelObj#new tries to get and crate constants that belongs to a module, but it does it inheriting. The change just avoids inheriting.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant