-
Notifications
You must be signed in to change notification settings - Fork 29
/
Copy pathfeed.xml
106 lines (93 loc) · 8.25 KB
/
feed.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.3.1">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2023-05-23T02:06:24-04:00</updated><id>/feed.xml</id><title type="html">Graphiti</title><subtitle>Stylish Graph APIs
</subtitle><entry><title type="html">Tutorial Write-Ups Are Out!</title><link href="/2019/10/14/tutorial.html" rel="alternate" type="text/html" title="Tutorial Write-Ups Are Out!" /><published>2019-10-14T00:00:00-04:00</published><updated>2019-10-14T00:00:00-04:00</updated><id>/2019/10/14/tutorial</id><content type="html" xml:base="/2019/10/14/tutorial.html"><p>Though we’ve long had a <a href="https://github.com/graphiti-api/employee_directory">sample application</a> with step-by-step diffs, we’ve been missing a full walkthrough. That now exists! Start with <a href="https://www.graphiti.dev/tutorial/step_0">Step 0: Bootstrapping</a>.</p>
<p>These write-ups will tell you the relevant code and commands, but
they’ll also give helpful context around the decisions Graphiti makes.
Even if you’re already a Graphiti user, I suggest checking it out!</p>
<p><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br /></p></content><author><name>Lee Richmond</name></author><summary type="html">Though we’ve long had a sample application with step-by-step diffs, we’ve been missing a full walkthrough. That now exists! Start with Step 0: Bootstrapping.</summary></entry><entry><title type="html">Graphiti 1.2 Released</title><link href="/2019/05/20/graphiti-1-2.html" rel="alternate" type="text/html" title="Graphiti 1.2 Released" /><published>2019-05-20T00:00:00-04:00</published><updated>2019-05-20T00:00:00-04:00</updated><id>/2019/05/20/graphiti-1-2</id><content type="html" xml:base="/2019/05/20/graphiti-1-2.html"><p>I’m thrilled to announce much-needed, much-improved Rails integration,
courtesy of the amazing <a href="https://github.com/wagenet">Peter Wagenet</a> and
the new <a href="https://github.com/graphiti-api/graphiti-rails">graphiti-rails</a> gem.
This gives us better error handling, tighter controllers, and a solid
foundation for the codebase moving forward.</p>
<p>You’ll be especially happy about this release if you’ve ever tried to
add error-handling middleware. Because prior versions of Graphiti used
<code class="highlighter-rouge">rescue_from</code> in <code class="highlighter-rouge">ApplicationController</code>, we intercepted errors before
other middleware had access to them. Now everything just works.</p>
<p>As part of this upgrade, we’re switching from <code class="highlighter-rouge">GraphitiErrors</code> to
<a href="https://github.com/wagenet/rescue_registry">RescueRegistry</a>. Think of
<code class="highlighter-rouge">RescueRegistry</code> as a well-refactored version of <code class="highlighter-rouge">GraphitiErrors</code>, available to
even non-Graphiti developers.</p>
<p>Though you don’t have to do anything to upgrade to Graphiti 1.2, this release will start throwing deprecation notices around <code class="highlighter-rouge">ApplicationController</code>. Don’t worry, the required changes are quite minor and spelled out in the <a href="https://www.graphiti.dev/guides/graphiti-rails-migration">graphiti-rails migration guide</a>.</p>
<p>I’m quite happy with how this effort turned out. This release dramatically improves our integration with Rails internals, and I think everyone involved learned a lot. I’m honored to work with such talented developers in our open-source community ❤️</p>
<p>If you have any further questions, check out the <code class="highlighter-rouge">#dev</code> or <code class="highlighter-rouge">#rails</code>
channels in our <a href="https://join.slack.com/t/graphiti-api/shared_invite/enQtMjkyMTA3MDgxNTQzLTU5MDI4MDllNTEzOTE1Nzk0ZGJlNTcxZDYzMGY2ZTczMDY2OWZhM2RmNTU0YWNiOWZhZDhkMmU4MzQ5NzIyNWM">Slack Chat</a></p>
<p><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br /></p></content><author><name>Lee Richmond</name></author><summary type="html">I’m thrilled to announce much-needed, much-improved Rails integration, courtesy of the amazing Peter Wagenet and the new graphiti-rails gem. This gives us better error handling, tighter controllers, and a solid foundation for the codebase moving forward.</summary></entry><entry><title type="html">Graphiti 1.1 Released</title><link href="/2019/05/08/graphiti-1-1.html" rel="alternate" type="text/html" title="Graphiti 1.1 Released" /><published>2019-05-08T00:00:00-04:00</published><updated>2019-05-08T00:00:00-04:00</updated><id>/2019/05/08/graphiti-1-1</id><content type="html" xml:base="/2019/05/08/graphiti-1-1.html"><p>Our first minor version bump centers around an important update:
<strong>better errors for clients</strong>. This is the first phase of work to allow us to provide more actionable errors to API users who might not also be developers of the API itself. This was brought to us by Graphiti maintainer <a href="https://github.com/wadetandy">Wade Tandy</a>.</p>
<p>Previously, when a client sent a bad write request to the server -
unwritable attributes/relationships, or bad types - we would render the
same generic 500 error JSON. We now render helpful error messages, so
third-party clients know how to correct their requests.</p>
<p>This is currently only affecting invalid writes, but the foundation laid
will be extendable to reads as well.</p>
<p><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br /></p></content><author><name>Lee Richmond</name></author><summary type="html">Our first minor version bump centers around an important update: better errors for clients. This is the first phase of work to allow us to provide more actionable errors to API users who might not also be developers of the API itself. This was brought to us by Graphiti maintainer Wade Tandy.</summary></entry><entry><title type="html">Graphiti 1.0 Released 🎉</title><link href="/2019/03/31/graphiti-1-0.html" rel="alternate" type="text/html" title="Graphiti 1.0 Released 🎉" /><published>2019-03-31T00:00:00-04:00</published><updated>2019-03-31T00:00:00-04:00</updated><id>/2019/03/31/graphiti-1-0</id><content type="html" xml:base="/2019/03/31/graphiti-1-0.html"><p>This project has gone through a number of iterations over the past three years. I’m happy to say we’ve now released 1.0, committing to semantic versioning. Graphiti has now seen enough use, across a wide variety of scenarios, that we can commit to no backwards-incompatible changes for a long while, and a changelog for future releases.</p>
<p>We’ll be writing more in this blog about our future roadmap. Stay tuned!</p>
<p><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br /></p></content><author><name>Lee Richmond</name></author><summary type="html">This project has gone through a number of iterations over the past three years. I’m happy to say we’ve now released 1.0, committing to semantic versioning. Graphiti has now seen enough use, across a wide variety of scenarios, that we can commit to no backwards-incompatible changes for a long while, and a changelog for future releases.</summary></entry></feed>