leoloso

9 ms·

61.
Gato GraphQL Webinar Series WPBuilds (In 48 Hs)(gatographql.com)
1 points by leoloso 3y ago|0 comments
62.
Things (you didn’t know) you can do with GraphQL in WordPress(gatographql.com)
1 points by leoloso 3y ago|0 comments
63.
Show HN: Gato GraphQL – a tool to interact with data in WordPress(github.com)
4 points by leoloso 3y ago|0 comments
64.
Show HN: Released v1.0 of Gato GraphQL (For WordPress)(github.com)
1 points by leoloso 3y ago|0 comments
65.
Why did my software take 1.5 years to be released?(graphql-api.com)
3 points by leoloso 4y ago|0 comments
66.
by leoloso 4y ago
1. I do already have the `Node` interface, but it's called `IdentifiableObject` as I cannot follow the convention, because the interface has 2 fields: - id: the actual WordPress ID - globalID And the convention says that Node can have
67.
by leoloso 4y ago
Check my response above to Kwpolska
68.
by leoloso 4y ago
The easy use case is to fetch data from a WordPress backend, and render your site using some JS library (React, Vue, Next.js). But it can do much more than that (indeed, I like to think of GraphQL as the single tool to deal with any content
69.
by leoloso 4y ago
I will not say why this plugin may be better as I'm naturally biased, but you can check the features from both plugins (mine under https://graphql-api.com/features/ ) and see how they compare. I haven't tried,
70.
by leoloso 4y ago
> I think it's an attempt to convey the level of effort involved Exactly this. Also it's a way to point out that I took no shortcuts. When you have a deadline with a client, you start dropping features out, and adding @todos to
71.
by leoloso 4y ago
check my response above
72.
by leoloso 4y ago
There was a lot of rewriting stuff to make the engine GraphQL-first. Before, the engine received a different spec as input, and GraphQL worked behind an adapter. Now, the engine speaks GraphQL language. Then completing the GraphQL schema, f
73.
Show HN: New GraphQL API for WordPress(github.com)
65 points by leoloso 4y ago|27 comments
74.
I run Integration Tests for my WP plugin using Lando and InstaWP(masterwp.com)
2 points by leoloso 4y ago|0 comments
75.
What you need to know about the Block Protocol(blog.logrocket.com)
1 points by leoloso 4y ago|0 comments
76.
Some great stuff I’ve learnt from WordCamp Europe 2022(masterwp.com)
1 points by leoloso 4y ago|0 comments
77.
Should GraphQL Be Different for Different Users?(graphql-api.com)
5 points by leoloso 4y ago|0 comments
78.
Some great stuff I’ve learnt from WordSesh 2022(masterwp.com)
1 points by leoloso 4y ago|0 comments
79.
Would WordPress be better off by Joining the Block Protocol?(masterwp.com)
2 points by leoloso 4y ago|0 comments
80.
Costs of WordPress Joining the Block Protocol(masterwp.com)
2 points by leoloso 4y ago|0 comments
81.
Exploring the future potential of generic GraphQL error codes(blog.logrocket.com)
2 points by leoloso 5y ago|0 comments
82.
Using the WordPress Editor and CPTs to Configure Plugins(smashingmagazine.com)
1 points by leoloso 5y ago|0 comments
83.
Implications of WordPress Joining the Block Protocol(smashingmagazine.com)
2 points by leoloso 5y ago|0 comments
84.
Fetching dynamically structured data in a CMS with GraphQL(blog.logrocket.com)
1 points by leoloso 5y ago|0 comments
85.
Phabel vs. Rector: Which is better for transpiling PHP code?(blog.logrocket.com)
1 points by leoloso 5y ago|0 comments
86.
What’s new in the latest GraphQL spec(blog.logrocket.com)
2 points by leoloso 5y ago|0 comments
87.
When to use multiple endpoints in GraphQL(blog.logrocket.com)
1 points by leoloso 5y ago|0 comments
88.
What we can learn from GraphQLConf 2021(blog.logrocket.com)
3 points by leoloso 5y ago|0 comments
89.
Field Arguments vs. Directives in GraphQL(blog.logrocket.com)
2 points by leoloso 5y ago|0 comments
90.
Categorizing GraphQL Directives into Schema or Query Type(stepzen.com)
1 points by leoloso 5y ago|0 comments

More ›