Azure Cosmos DB with Gremlin API does not support fluent API yet, it was further postponed to first half of 2020.
As a workaround, we are using the translator to submit fluent api queries as 'script'.
However, we cannot initialize a translator that works with Azure's CosmosDB based based on an AnonymousTraversalSource or GraphTraversalSource, this type must allow for the 'string' possibility.
The correct usage with Azure's cosmos db is:
```
const translator = new gremlin.process.Translator('g' as any);
```
Currently this works.
Related stackoverflow thread:
https://stackoverflow.com/questions/58815569/azure-cosmos-gremlin-nodejs-how-to-submit-fluent-query-as-script-not-bytecod/59056304#59056304
* Add .include aliases to Deep, Nested, and Own
chai.d.ts missing .include aliases in Deep, Nested, and Own interfaces
* Only Deep changes are tested
* Test .deep.include aliases
* Add .include aliases to Nested and Own
This declares the useDataPageV2 option, which must be set to false for compatibility with the C++ (and possibly other) implementation of parquet. BigQuery, for example, does not seem to support the V2 data page.
At the same time I factored out the options to an interface, to reduce duplication.
* add session? to QueryFindOneAndUpdateOptions interface
Needed to run findOneAndUpdate inside of a transaction
* add session param to QueryFindOneAndRemoveOptions
* Adjust polymer attributeChangedCallback to spec.
According to the specification at:
https://html.spec.whatwg.org/multipage/custom-elements.html#custom-element-reactions
`attributeChangedCallback` is called "given the attribute's local name,
old value, new value, and namespace as arguments". This also matches
browser implementations and understanding of how things work from
discussion with Polymer engineers (CC @rictic).
* Fix a dtslint issue with TypeScript <3.0.
TypeScript 3.0 and before appears to be confused with the `extends`
property declared here.
* parse: Fix tslint issues
* parse: Update ts test cases
* parse: Stricter types for Parse.Object attributes
* Better constructor handling for Parse.Object
* Use keyof T for more attribute parameters and add tests
* parse: Improve Parse.Object method types and add more tests
* Remove Parse.VERSION type as it does not exist in documentation
* Add references for other declaration files to index.d.ts
* parse: Fix constructor types for classes that extend Parse.Object
* parse: Fix Parse.Object child classes
* Return Parse functions to old location for more readable diff
* parse: Remove for import
* parse: Lint fixes
* parse: Revert to old module declarations for easier diff
* New require: true documentation
* Remove removed methods
* Add myself to definitions by
* Update version header
* Run prettier
* Add visibility param to Model.toJSON
* [styled-components] Allow static properties to be passed through
* lint
* fix tests
* hoist-non-react-statics like original lib
* fix lint
* fix tests
* remove dependency as it is not required if inside @types anyways
* rm comma
* @types/stripe-v3 Element addEventListener and on is alias of eachother
`this.on=this.addListener=this.addEventListener=n` from https://js.stripe.com/v3/
And the documentation for the on-method uses the addEventListener in its exemple.
https://stripe.com/docs/stripe-js/reference#the-element
* stripe-v3: add test for addEventListener()
* stripe-v3: re-order due to linting error
* added 2nd test
Previously good code wouldn't compile because both `props` used
definitions without `React.HTMLProps` which is the correct definition for
the `props object` mentioned in https://github.com/conorhastings/react-syntax-highlighter#props.
All `lineProps` and `codeTagProps` tests have now explicitly defined
`prop` type.
* Added "compact" option to Globalize's CommonNumberFormatterOptions.
This option was introduced with Globalize 1.4.0
* Fixed indentation
Switched from spaces to tabs for consistency with the rest of the file
Lyanbin