GithubHelp home page GithubHelp logo

shahareli / requestfieldsselector Goto Github PK

View Code? Open in Web Editor NEW
3.0 2.0 1.0 3.69 MB

Determine the data you want to get from your client just like GraphQL with easy to plug express middleware!

License: MIT License

JavaScript 7.20% Shell 0.94% TypeScript 91.86%

requestfieldsselector's Introduction

Contributors Forks Stargazers Issues MIT License


Logo

Request fields selector

Determine the data you want to get from your client just like GraphQL with easy to plug express middleware!

View Examples Β· Report Bug Β· Request Feature

Table of Contents
  1. About The Project
  2. Motivation
  3. Installation
  4. Usage
  5. Roadmap
  6. Contributing
  7. License
  8. Contact
  9. Acknowledgements

About The Project

The requestFieldsSelectorMiddleware provide an easy way to pick the fields of the response you send from the api in your client! just like GraphQl and even with the same syntax. The middleware improve your api by reducing over-fetching and less data transportation. Designed to use in any express api.

Motivation

I was getting sick of making many if else statements to reduce the data transportation from my api to my client and GraphQl doesn't always fit in the project type so I wanted to make an easy way to improve all my servers with the advantages of GraphQl.

Installation

npm install request-fields-selector

Usage

For more examples, please refer to the Project`s tests and Example server

  • First add the request-fields-selector middleware to your server above all the crud routes:
import requestFieldsSelectorMiddleware from 'request-fields-selector'

const app = express()

app.use(express.json())
app.use(requestFieldsSelectorMiddleware)
// You can add config object
 app.use((...args) => requestFieldsSelectorMiddleware(...args,
 {
  silent: true //no error logs
  dataNestedField: "data" // e.g your response look like this {data:"your data",status:"ok",...} the value that will be transformed will be data
  fieldSelectorName: "customFieldsName" // the default fields will be taken from your req.query or req.body and called "fields"
 }
 ))
  • Then in your client:
const API_URL = "http://happy";
const data = await fetch(`${API_URL}?fields=
{
  book {
    author
  }
}`);

//or as one liner
const data = await fetch(`${API_URL}?fields={book{author}}`);
//in the post method:
const fields = `
{
 book{
   id
   author{
     firstName
   }
 }
`;
const data = await fetch({
  method: "POST",
  body: JSON.stringify({ ...body, fields }),
});
  • Then in your api routes:
app.get("/", (req: Request, res: Response) => {
  const { transform } = req; // the middleware will provide transform function that will match the client fields to the data you about to send - if error happen it will send the whole data
  res.json(transform(data));
});

Roadmap

See the open issues for a list of proposed features (and known issues).

Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Follow the commits and linting guides (conventional commits and eslint)
  6. Open a Pull Request
  7. Make sure that the pull request passed all the workflows

License

Distributed under the MIT License. See LICENSE for more information.

Contact

Shahar Eliyahu - mail

Project Link: https://github.com/ShaharEli/requestFieldsSelector

Acknowledgements

requestfieldsselector's People

Contributors

shahareli avatar

Stargazers

Rod Kisten (Costa) avatar Atle Hansson avatar Koren avatar

Watchers

Taylor Buckner avatar  avatar

Forkers

korenezri

requestfieldsselector's Issues

Remove dependency on express

The dependency on express locks this into a specific version major/minor version of express. Removing this dependency would allow more flexibility.

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.