Download the PHP package forikal/gsheet-to-xml without Composer
On this page you can find all versions of the php package forikal/gsheet-to-xml. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download forikal/gsheet-to-xml
More information about forikal/gsheet-to-xml
Files in forikal/gsheet-to-xml
Package gsheet-to-xml
Short Description Command for parsing Google Drive URLs and converting sheets to XML.
License Apache-2.0
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package gsheet-to-xml
sheet-to-xml
Symfony Console command that, given the URL of a (specifically structured) Google Sheet or Google Drive folder of sheets, outputs the contents (perhaps in multiple tabs) in the form of Xml.
Designed be used in the context of the Symfony Console application at https://github.com/xmlsquad/xml-authoring-tools which, in turn, is used in the context of a known directory structure which is based on xml-authoring-project.
Documentation
See: https://github.com/xmlsquad/gsheet-to-xml/blob/master/DOCUMENTATION.md
Original Specification:
Schema descriptions
I have published
- a schema defining how the Google Sheets map to Xml.
- an example Inventory sheet.
- an example Xml representation of Inventory data.
- some of the rules that define the valid structure of an Inventory sheet.
Naming convention.
Given a Google Sheet, unless the sheet's name implies it is 'ignored', it is assumed that its structure is valid structure of an Inventory sheet. Given a Google Drive folder, it is assumed that any Google Sheets found within have the valid structure of an Inventory sheet (unless the sheet's name implies it is 'ignored').
A Google sheet's with a trailing underscore in their name imply that it should be 'ignored'. A Google sheet tab's with a trailing underscore in their name imply that it should be 'ignored'.
If a file is called foo, then it is validated as normal.
If a file is called foo_, then it is assumed to be 'private' and should be explicitly ignored, but it should be noted (in any feedback) that it was ignored.
If a Google Sheet's tab is named foo, then it is validated as normal.
If a Google Sheet's tab is named foo_, then it is assumed to be 'private' and should be explicitly ignored, but it should be noted (in any feedback) that it was ignored.
Input
-
driveUrl: The URL of the Google Drive entity (Google Sheet or Google Drive folder).
- is-recursive: if the Google Drive entity is a Google Drive folder, this option specifies whether or not to recurse through sub-directories to find sheets.
Behaviour
If the driveUrl is a Google Sheet write out the contents as Xml.
If it is a Google Drive find all Google Sheets within the directory (recursively, if specified) and write out the contents as Xml.
Output
STD_OUT
Streamed output.
Xml representation of the Inventory data in the Google Sheet.
All versions of gsheet-to-xml with dependencies
google/apiclient Version ^2.0
symfony/console Version ~3.4
xmlsquad/xml-authoring-library Version 0.3.3