profile
viewpoint
Kevin Berry lostmarinero San Francisco http://www.kevinberry.soy Non-profits and technology

kmazanec/parking-danger-map 8

See parking tickets issued on a heatmap and submit your own

kmazanec/adopt-a-coder 7

A crowd-sourced scholarship platform for tech bootcamps.

codeforamerica/ReqCheck 6

ReqCheck Project, developed by the Code for America's 2016 Kansas City, Missouri (KCMO) Fellowship Team in collaraboration with the KCMO Health Department.

lostmarinero/diffux 1

A tool to diff website snapshots

maryamq/SafeBridge 1

ChimeHack

push eventlostmarinero/todo-api

Kevin Berry

commit sha d1269b2d36db70e44fd9e81b773cb7cf41b74cc1

Update db.json

view details

push time in a month

push eventlostmarinero/todo-api

Kevin Berry

commit sha 2418aa04b68204e34cca1564ee2b5ebc3b03f937

Update db.json

view details

push time in a month

create barnchlostmarinero/todo-api

branch : master

created branch time in a month

created repositorylostmarinero/todo-api

created time in a month

issue commentmui-org/material-ui

TablePagination warning when page is out of range

Have you all considered if someone has a largeish data set and wants to be able to start in the middle, how to handle it? For example, if I have 1000 records and i do the page length of 50 per page, and i want to start at page 10 (without having to pre-load 500 records), how could i accomplish this?

I was trying to do so with using queryParams (pageNumber), and then loading the page via the api, however if I use pageNumber in with the TablePagination, I get: index.js:1 Warning: Failed prop type: Material-UI: the page prop of a TablePagination is out of range (0 to 0, but page is 1).

eps1lon

comment created time in 2 months

issue commenthowtographql/graphql-ruby

TypeError: Cannot read property 'types' of undefined when completeing tutorial on https://www.howtographql.com/graphql-ruby/2-queries/

Circling back, I was migrating from a REST based API to Graphql. My old project had a middleware (https://github.com/vigetlabs/olive_branch) which I had forgotten to disable, so this was causing it to auto change snake case (which it identified __schema as snake case) to CamelCase. My bad about this, but wanted to follow up in case anyone else had issues, maybe check your middlewares.

kaspar-naaber

comment created time in 2 months

issue commenthowtographql/graphql-ruby

TypeError: Cannot read property 'types' of undefined when completeing tutorial on https://www.howtographql.com/graphql-ruby/2-queries/

I recently got this error. I am running rails 6, graphiql-rails (1.7.0) and graphql (1.10.5). I had built it as an API but then added the necessary configurations to run graphiql in local development, including adding an app/assetts/config/manifest.js with

//= link_tree ../images
//= link_directory ../javascripts .js
//= link_directory ../stylesheets .css

The error I am receiving is:

TypeError: Cannot read property 'types' of undefined
    at buildClientSchema (http://localhost:3000/assets/graphiql/rails/application-6f03c7a92432765b0fbe671bfb7a292ee6c37e6704b6e6ac95587e45676bbf72.js:34102:72)
    at http://localhost:3000/assets/graphiql/rails/application-6f03c7a92432765b0fbe671bfb7a292ee6c37e6704b6e6ac95587e45676bbf72.js:2795:55

I tried deleting my graphql directory and re-doing the rails generate graphql:install.

I was able to look into it more - I made a breakpoint in the chrome debugger for line 34,102, which has the following code:

function buildClientSchema(introspection, options) {
  // Get the schema from the introspection result.
  var schemaIntrospection = introspection.__schema;

  // Converts the list of types into a keyMap based on the type names.
  var typeIntrospectionMap = (0, _keyMap2.default)(schemaIntrospection.types, function (type) {
    return type.name;
  });
..... more code ......

The issue is with schemaIntrospection.types, schemaIntrospection is undefined. So above, I inspected the introspection variable which calls introspection.__schema - The introspection variable looked like:

{"Schema":
    {"queryType": {"name":"Query"},
     "mutationType": {"name":"Mutation"},
     "subscriptionType":null,
.... more JSON ...

So, what I ended up doing is instead of having var schemaIntrospection = introspection.__schema;, I set the schemaIntrospection variable using the correct key:

var schemaIntrospection = introspection.Schema;

And it worked! For that specific call only :/ , as I had used the interactive debugger

Does anyone know how I can fix this with ruby-graphql more permanently?

I want to be able to use the Documentation Explorer

Thanks!

kaspar-naaber

comment created time in 2 months

push eventlostmarinero/lostmarinero.github.io

Kevin Berry

commit sha 804394a530441e83dc454ea11d17774abd0545ad

update

view details

push time in 2 months

push eventlostmarinero/lostmarinero.github.io

Kevin Berry

commit sha c2be68247fe9c2bf5b9d272df6396e46dd6ecd9d

update

view details

push time in 2 months

push eventlostmarinero/lostmarinero.github.io

Kevin Berry

commit sha d5ccd0aed4cfa39e761e1bb5e332ea66edaec322

Update

view details

push time in 2 months

startedkentcdodds/bookshelf

started time in 2 months

pull request commentsiriwatknp/mui-treasury

#398 typescript support

+1 for typescript support! Would love to see this added

siriwatknp

comment created time in 2 months

more