[SERVER-55317] Inconsistent naming for API version parameters Created: 18/Mar/21  Updated: 29/Oct/23  Resolved: 06/Apr/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.9.0-alpha4
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Minor - P4
Reporter: Oleg Pudeyev (Inactive) Assignee: Xuerui Fa
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-55791 Update API parameters references to m... Backlog
Backwards Compatibility: Minor Change
Operating System: ALL
Steps To Reproduce:

Run

{getParameter:1}

and inspect the keys.

Sprint: Repl 2021-04-19
Participants:

 Description   

4.9.0-alpha5 server offers the following parameters:

 "acceptAPIVersion2"=>false,
 "requireApiVersion"=>false,

As a user of the server I would like the server to use consistent case for related parameters, i.e. either use API or Api for both (and all of the other API version-related parameters).



 Comments   
Comment by Githook User [ 06/Apr/21 ]

Author:

{'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}

Message: SERVER-55317: Use consistent case when naming user-facing API parameters
Branch: master
https://github.com/mongodb/mongo/commit/dfbc1ce544549c95644cd64f74dbea8b55e2cd3c

Generated at Thu Feb 08 05:36:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.