Why doesn't python client have syn.buildTable() when R client has synBuildTable()?
Description
Build table function can be found in
synapseclient.table.build_table()
Environment
Activity
Was the naming a mistake or did our R users ask for this feature? I think this function is being used in R, but I'm not entirely sure.
arguably, this should be changed in R, not Py, to restore parity. But we also have to be careful not to make a breaking API change in the R client.
I think the naming was mistaken on the R side. Either that or we should not document that synFuncName() in R translates directly to syn.funcName() in Python
synapseclient.table.build_table is a static helper function that not relevant to the synapseclient.client.Synapse class. I'd rather not keep tagging on unrelated static function shortcuts onto the synapseclient.client.Synapse class each time we expose a helper function in the R client just to maintain the naming parity. That would make synapseclient.client.Synapse even messier than it already is.
I think the build_table function was exposed in the R client people to have a way to build tables programmatically in the R client. Im not exactly sure why there is a difference, but should I reopen?
