graphql-to-parsequery
v1.0.1
Published
Utility functions that convert GraphQL statements (e.g. `where`) into Parse.
Downloads
1
Readme
graphql-to-parsequery
Utility functions that convert GraphQL statements (e.g. where
) into Parse.
Functions
All utility functions can be imported from named imports:
import { functionName } from 'graphql-to-parsequery';
Or tree shakeable imports:
import { functionName } from 'graphql-to-parsequery';
tranformGraphQLWhereToParse
This function transforms a GraphQL where statement into a Parse query input constraint. Example:
let where = {
author: {
have: {
username: {
equalTo: '[email protected]',
},
},
},
};
transformGraphQLWhereToParse(where, 'BlogPost', parseClasses);
console.log(where);
/* output:
{
author: {
$inQuery: {
where: {
username: {
$eq: '[email protected]',
},
},
className: '_User',
},
},
}
*/
You can find out more about this function and all other functions here.
Want to contribute?
This package was bootstrapped using TSDX, and all major functions are exported out of /src/index.ts
To run TSDX, use:
npm start # or yarn start
This builds to /dist
and runs the project in watch mode so any edits you save inside src
causes a rebuild to /dist
.
To do a one-off build, use npm run build
or yarn build
.
To run tests, use npm test
or yarn test
.
Configuration
Code quality is set up for you with prettier
, husky
, and lint-staged
. Adjust the respective fields in package.json
accordingly.
Jest
Jest tests are set up to run with npm test
or yarn test
.
Bundle Analysis
size-limit
is set up to calculate the real cost of your library with npm run size
and visualize the bundle with npm run analyze
.
Setup Files
This is the folder structure we set up for you:
/src
index.tsx # EDIT THIS
/test
blah.test.tsx # EDIT THIS
.gitignore
package.json
README.md # EDIT THIS
tsconfig.json
Rollup
TSDX uses Rollup as a bundler and generates multiple rollup configs for various module formats and build settings. See Optimizations for details.
TypeScript
tsconfig.json
is set up to interpret dom
and esnext
types, as well as react
for jsx
. Adjust according to your needs.
Continuous Integration
GitHub Actions
main
which installs deps w/ cache, lints, tests, and builds on all pushes against a Node and OS matrixsize
which comments cost comparison of your library on every pull request usingsize-limit
Optimizations
Please see the main tsdx
optimizations docs. In particular, know that you can take advantage of development-only optimizations:
// ./types/index.d.ts
declare var __DEV__: boolean;
// inside your code...
if (__DEV__) {
console.log('foo');
}
You can also choose to install and use invariant and warning functions.
Module Formats
CJS, ESModules, and UMD module formats are supported.
The appropriate paths are configured in package.json
and dist/index.js
accordingly. Please report if any issues are found.
Named Exports
Per Palmer Group guidelines, always use named exports. Code split inside your React app instead of your React library.
Including Styles
There are many ways to ship styles, including with CSS-in-JS. TSDX has no opinion on this, configure how you like.
For vanilla CSS, you can include it at the root directory and add it to the files
section in your package.json
, so that it can be imported separately by your users and run through their bundler's loader.
Publishing to NPM
We recommend using np.