graphql-mimic's Introduction

Hey! 👋 I'm Daniel Fernández

👨🏻‍💻 Web/Frontend Developer

I've been doing software engineering for 10+ years, during which I have gained valuable knowledge and experience developing and architecting web applications for small, medium and large sized companies. I really enjoy creating high-quality web applications using tools like React and NodeJS but I will be happy to jump and learn new technologies at any moment.

I've had the privilege of working across different markets, both in Europe and the Americas, gaining valuable insights into the unique challenges and opportunities that each region offers. This global perspective has enriched my approach to problem-solving and software development.``

I also enjoy and have experience leading engineering teams and working with stakeholders to build successful software products.

In case you still want to know more about me 👉

graphql-mimic's People

Contributors

Stargazers

Watchers

graphql-mimic's Issues

GraphQL client agnostic?

@dfernandeza 👋

Is graphql-mimic client agnostic or should we provide "adapter" for Apollo first with a clear interface - if possible - for people wanting to use it with other clients?

I am asking because I would see myself wanting to mock existing query in my application components that rely a lot on Apollo's useQuery(), etc

Example usage with Apollo (using your README example):

myComponent.ts

const QUERY = gql`
  query {
    characters {
      results {
        id
        name
      }
    }
  }
`;

const MyComponent = () => {
   const { data } = useQuery(QUERY)
   return (
      <div>
         {data.characters.results.map((c) => <div className="name">${c.name}</div>)}
      </div>
   )
}

myComponent.spec.ts

import { shallow } from 'enzyme';
import * as schema from "./schema.json";
import MyComponent from 'src/MyComponent"


// <MimicProvider> provides a test <ApolloProvider> for testing
const MimicProvider = Mimic.Provider({ schema });

describe('MyComponent', () => {
   it('renders 2 items', () => {
      const wrapper = shallow(<MimicProvider><MyComponent /></MimicProvider>);
      expect(wrapper.find('.name')).to.have.lengthOf(2);
   });  
})

Mocking resolvers

I like your idea to fallback to default data given the type.
I would also propose:

Ability to configure resolved data given a GraphQL scalar Type: Int, String, etc
Ability to configure resolved data given GraphQL object type and fields: User.name, etc

Open questions:

How should be handle nullable field by default?

Recommend Projects

dfernandeza / graphql-mimic Goto Github PK

graphql-mimic's Introduction

Hey! 👋 I'm Daniel Fernández

graphql-mimic's People

Contributors

Stargazers

Watchers

graphql-mimic's Issues

GraphQL client agnostic?

Mocking resolvers

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent