velir / kaltura-ruby Goto Github PK

• reference_id
• replacing_entry_id
• replaced_entry_id
• replacement_status
• partner_sort_value
• conversion_profile_id

These need to be added in.

Kaltura::ClassFactory is currently very fragile. Any additions to the response schema causes the library to stop functioning.

The most ideal solution is to define an accessor and setter to the class dynamically when it encounters an attribute that can't be handled by the object being constructed. Other Kaltura libraries tend to just ignore the NoMethod exception, but this will carry a performance penalty in Ruby. Only the first request will have to climb all they way up the ancestor chain to Object.

hi,
i've been using your library for a while now. i'm loving your version and i'm sure this is going to be much better than the official one.

just wondering have you faced such problem before ?

i wrote ...kaltura_client.flavor_params_service.list it threw up the following message -

Failure/Error: p Video.kaltura_client.flavor_params_service.list
     NoMethodError:
       undefined method `system_name=' for #<Kaltura::FlavorParams:0x00000106398300>

Perhaps a new Kaltura change is causing some new errors? I am seeing errors from the gem such as:

NoMethodError: undefined method `root_entry_id=' for #Kaltura::BaseEntry:0x002aeffd283b70

Where:
[GEM_ROOT]/gems/velir_kaltura-ruby-0.4.10/lib/kaltura/kaltura_client_base.rb, line 253

Seems similar to this: #2

Thanks.

-- Jason