The latest articles on DEV Community by eprince1 (@eprince1). https://dev.to/eprince1 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F226879%2Fdf767634-fd09-4003-b137-b12951a1c7b8.png https://dev.to/eprince1 en eprince1 Mon, 03 Apr 2023 18:40:33 +0000 https://dev.to/eprince1/instantly-generate-graphql-documentation-with-doqlize-268h https://dev.to/eprince1/instantly-generate-graphql-documentation-with-doqlize-268h <p>GraphQL is quickly becoming one of the most popular query languages for APIs due to its flexibility and efficiency. However, documenting GraphQL APIs can be a tedious and time-consuming process. That's where <a href="https://www.doqlize.com">doQLize</a> comes in.</p> <p><a href="https://res.cloudinary.com/practicaldev/image/fetch/s--2S2YA4OO--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/t8m1e9pr5alx4ln6qldm.png" class="article-body-image-wrapper"><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--2S2YA4OO--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/t8m1e9pr5alx4ln6qldm.png" alt="doqlize api example" width="880" height="470"></a></p> <p><a href="https://www.doqlize.com">doQLize</a> is a SaaS tool that instantly generates readable GraphQL documentation. With <a href="https://www.doqlize.com">doQLize</a>, developers can create accurate and up-to-date documentation for their GraphQL APIs without any manual work.</p> <p>The tool works by analyzing the GraphQL schema and generating detailed documentation that is easy to read and understand. It provides a clear and concise overview of the available queries, mutations, subscriptions, and types. In addition, <a href="https://www.doqlize.com">doQLize</a> also generates examples of how to use each query, mutation, and subscription, making it easier for developers to integrate their APIs.</p> <p>One of the biggest advantages of <a href="https://www.doqlize.com">doQLize</a> is its ability to organize your documentation similar to how a REST API would be documented. Instead of organizing by query, mutation, and subscription, <a href="https://www.doqlize.com">doQLize</a> organizes by action and categories so that developers can easily understand your API.</p> <p>Some upcoming features include</p> <ul> <li>Fully custom domains</li> <li>Hide/Show specific graphql sections</li> <li>CI/CD pipeline</li> <li>Viewing metrics and insights</li> <li>Custom branding</li> <li>"Search Everything"</li> <li>No api size limit</li> </ul> <p>With doQLize, developers can save time and focus on what really matters - building great products.</p> <p>doQLize is currently in its MVP state and is free to use. We are looking for interest and feedback and hope you give it a try!</p> graphql webdev devops saas eprince1 Wed, 11 Sep 2019 22:00:34 +0000 https://dev.to/eprince1/manage-pull-requests-with-mergefly-39oa https://dev.to/eprince1/manage-pull-requests-with-mergefly-39oa <h3> <strong>My Frustrations With Pull Requests</strong> </h3> <p>I am going to argue that pull requests are the most important part of the development life-cycle. It is the only chance I get to see and comment on the code my fellow developers are writing. It is when design decisions are finalized, edge cases are discovered and code quality is enforced by you and your teammates. But, as vital as pull requests are for keeping a team's code solid, I often found myself frustrated by how limiting the tools are.</p> <p>A few examples include:</p> <ul> <li>Only the immediate lines surrounding code changes are provided which is often not enough context</li> <li>Comments break up the lines of code making changes very difficult to read</li> <li>Files are displayed as a giant list which makes it hard to find the one I am looking for</li> <li>I have to reload the page in order to load updates to the review</li> <li>In general the UI is messy and confusing</li> </ul> <p>I have heard my teammates complain that they "dont trust code reviews because they are not able to see the whole picture.” But, I have always felt that this wouldn’t be a problem with a good user interface.</p> <p>My brother and I took it upon ourselves to tackle this problem. Being developers ourselves, we knew the pain points and we set out to create a tool that we would be excited to use every day. We focused on providing the most amount of context surrounding code changes with a UI that resembled an IDE.</p> <p>One year later, we are proud to present to you our solution: Mergefly.</p> <p><a href="https://www.youtube.com/watch?v=mI_R35AnXAk&amp;t">Mergefly Promotion Video</a></p> <h3> <strong>Comments</strong> </h3> <p><strong>Comments are completely revamped.</strong> On GitHub, comments are built into the location of the code. This interrupts the flow of reading code because once you have multiple comments, the code is completely broken up. The comments themselves are also not searchable making it difficult for me to find specific comments I had already left.</p> <p>We fixed this by pulling the comments out of the code itself. You can now view comments in a modal you can drag around or on the side of the page. You can also jump directly to the code based off of a comment to review pull requests faster.</p> <p><a href="https://res.cloudinary.com/practicaldev/image/fetch/s--5P5-W_Js--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/10jr613cwu06ww2b9x6u.png" class="article-body-image-wrapper"><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--5P5-W_Js--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/10jr613cwu06ww2b9x6u.png" alt="Alt Text"></a></p> <h5> <strong>Highlights</strong> </h5> <ul> <li>View comments either in an adjustable modal or off to the side</li> <li>Jump directly to specific code locations from a comment</li> <li>Comments are updated live</li> </ul> <h3> <strong>Navigation</strong> </h3> <p><strong>Navigation is seamless.</strong> Many times I found myself searching GitHub longer than I had to in order to accomplish simple tasks. This included searching for files, leaving reviews, opening repositories, filtering pull requests, and even merging. It was also frustrating to me how easily I could lose my place when I would update the page and GitHub automatically scrolled to the top.</p> <p>We designed Mergefly with all of these problems in mind. We can have multiple tabs on a single page so that you can switch between multiple reviews without losing your place. We have a file tree so you can see the hierarchy much more clearly. Lastly, pages auto update so you never have to refresh when changes occur in your repository.</p> <p><a href="https://res.cloudinary.com/practicaldev/image/fetch/s---u9uqPDs--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/ouqclg6dwcwuhb3vb7vy.png" class="article-body-image-wrapper"><img src="https://res.cloudinary.com/practicaldev/image/fetch/s---u9uqPDs--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/ouqclg6dwcwuhb3vb7vy.png" alt="Alt Text"></a></p> <p><a href="https://res.cloudinary.com/practicaldev/image/fetch/s--e2EyX8_q--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/hg3osxqaw373i33g4n59.png" class="article-body-image-wrapper"><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--e2EyX8_q--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/hg3osxqaw373i33g4n59.png" alt="Alt Text"></a></p> <h5> <strong>Highlights</strong> </h5> <ul> <li>Get to any repository or Pull Request without a page reload</li> <li>Switch between files, repositories, and Pull Requests instantly on the same page with multiple tabs</li> <li>Send your URL to a friend and they will open up to the same file and line you were looking at</li> </ul> <h3> <strong>Reviews</strong> </h3> <p>We gave reviews more meaning. I felt that GitHub reviews were under utilized and a little out of place. They have this odd status of a comment but you can’t reply to them so they get lost in the conversation feed. As a result I never understood the proper way to use them.</p> <p>We decided to turn reviews into a chat like system. This creates better notifications and more context for members looking at a pull requests. It also creates a location to discuss pull requests as a whole instead of specific lines of code.</p> <p><a href="https://res.cloudinary.com/practicaldev/image/fetch/s--ZB7skpWa--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/nw6vdp0siumpikgyipwn.png" class="article-body-image-wrapper"><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--ZB7skpWa--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/nw6vdp0siumpikgyipwn.png" alt="Alt Text"></a></p> <h4> <strong>Highlights</strong> </h4> <ul> <li>Reviews are kept in one place instead of scattered over the conversation history</li> <li>Reviews are faster and behave almost like a messaging app</li> </ul> <h3> <strong>More Features</strong> </h3> <p>This is really only scratching the surface. If you want to get a full picture of what Mergefly can do, check out all of our awesome features <a href="https://mergefly.com/features">here</a>!</p> <h3> <strong>Free to the Open Source Community</strong> </h3> <p>We made Mergefly to give developers more confidence when merging code. We want to reduce bugs and make the development life-cycle smoother for everyone.</p> <p>Check us out at <a href="https://mergefly.com">mergefly.com</a>!</p> github opensource productivity