Copy_to returning raw dictionary

Is your feature request related to a problem? Please describe. It would be great if we were able to initialize a worksheet from a json. Or alternatively have the worksheet.copy_to method return the worksheet instead of the raw dictionary returned by google

Below the example of a dict returned by the copy_to method. I would love to be able to immediately edit this worksheet.

json

{'sheetId': 1234556, 'title': 'titel', 'index': 6, 'sheetType': 'GRID', 'gridProperties': {'rowCount': 1003, 'columnCount': 25, 'frozenRowCount': 1, 'hideGridlines': True, 'columnGroupControlAfter': True}, 'tabColor': {'red': 0.9882353, 'green': 0.49019608, 'blue': 0.4117647}, 'tabColorStyle': {'rgbColor': {'red': 0.9882353, 'green': 0.49019608, 'blue': 0.4117647}}}

[lavigne958]

Hi, I looked at your issue and I am sorry but we can’t make it without extra costs.

The dict object returned by the API contains only the new sheet properties. it does not contain any informations about the spreadsheet where this sheet has been copied to.

I face 2 issues:

1. with only the sheet properties I could return a new Worksheet instance but we don’t have the parent Spreadsheet object that will do all the HTTP requests
2. the method copy_to takes the Spreadsheet ID so we could do something but in the end it will only be like any user could do: 1) open the destination spreadsheet 2) open the new worksheet.

About the protected ranges this is a good point, but we will tackle it in a different issue, see #1046

Closing this issue.

[juliusdanek]

Yeah, it’s costly unfortunately.