[RCBC-75] Provide Consistent Order of Parameters Created: 24/Aug/12  Updated: 01/May/14

Status: Open
Project: Couchbase Ruby client library
Component/s: None
Affects Version/s: None
Fix Version/s: None
Security Level: Public

Type: Improvement Priority: Major
Reporter: Sergey Avseyev Assignee: Matt Ingenthron
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Provide consistent, predictable order for method parameters as other SDKS.

Comment by Sergey Avseyev [ 24/Aug/12 ]
Could you extend your query please with examples? Where the API is inconsistent and unpredictable?
Comment by kzeller [ 27/Aug/12 ]
Here is the first example. This may require a fix on the Java side vs. the Ruby side:


Order is key, expiry, then value

Should be one fairly consistent order across the SDKs.

Will add others as either I or others (customer support) run across them.

Comment by kzeller [ 27/Aug/12 ]
I have reassigned this to Matt so this can be looked at globally post 2.0, and hopefully approached across the SDKs. This is a repeated request I am getting from customer support.
Generated at Wed Nov 26 10:15:15 CST 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.