<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Andrey</title>
    <description>The latest articles on DEV Community by Andrey (@avkonst).</description>
    <link>https://dev.to/avkonst</link>
    <image>
      <url>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%2F179811%2F2b663819-e051-4ef6-be40-24eb5ab67ec9.png</url>
      <title>DEV Community: Andrey</title>
      <link>https://dev.to/avkonst</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/avkonst"/>
    <language>en</language>
    <item>
      <title>A GitHub issue report which makes you happy</title>
      <dc:creator>Andrey</dc:creator>
      <pubDate>Fri, 20 Aug 2021 23:29:19 +0000</pubDate>
      <link>https://dev.to/avkonst/a-github-issue-report-which-makes-you-happy-1ff6</link>
      <guid>https://dev.to/avkonst/a-github-issue-report-which-makes-you-happy-1ff6</guid>
      <description>&lt;p&gt;I have processed many tickets in various issue tracking systems in my life. I prefer to categorize tickets to one or more of the following types:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Feature request&lt;/strong&gt;: for an open source project it is a great indicator that a project is wanted and new features drive the growth. No new features are added without an effort.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bug report&lt;/strong&gt;: well, it has to be addressed. And I follow the philosophy that bug reports should be addressed at higher priority than features. No bugs are fixed without an effort.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Question&lt;/strong&gt; (or &lt;em&gt;Misunderstanding&lt;/em&gt; reported as a bug): these usually highlight gaps in documentation (or unintuitive API / behavior). Users have to be guided and usually questions are answered by directing to an existing documentation, or documentation is improved as a result of a ticket. I do not like to receive the same question multiple times, so I try to improve documentation at higher priority than features. This type of ticket also requires the effort and time of a developer.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All of the above types of tickets require attention of project developers, and time and effort to address.&lt;/p&gt;

&lt;p&gt;However, today I received an issue report which did not require me to do anything about. It does not fall in any of the above categories. At the same time, I was happy this was submitted. The ticket is &lt;a href="https://github.com/avkonst/hookstate/issues/220"&gt;#220 for Hookstate library&lt;/a&gt;, which I believe is one of the best state management libraries for React. And the ticket's title is "Just want to share how much I love this library and how much time it has saved me".&lt;/p&gt;

&lt;p&gt;Fortunately, GitHub issue tracker does not have a mandatory field "Close reason", like (most of?) all JIRA-based trackers. So, I can just close it.&lt;/p&gt;

&lt;p&gt;However, I think closing it without an action would be rude :) So, I have decided to give it time in the form of writing this little post.&lt;/p&gt;

&lt;p&gt;How do you categorize tickets of a similar kind? And what action do you take before closing them?&lt;/p&gt;

</description>
      <category>github</category>
      <category>typescript</category>
      <category>react</category>
      <category>hookstate</category>
    </item>
    <item>
      <title>Hookstate: the modern, extremely fast and extendable state management for React that is based on hooks.</title>
      <dc:creator>Andrey</dc:creator>
      <pubDate>Tue, 20 Aug 2019 01:01:52 +0000</pubDate>
      <link>https://dev.to/avkonst/hookstate-the-modern-extremely-fast-and-extendable-state-management-for-react-that-is-based-on-hooks-4on8</link>
      <guid>https://dev.to/avkonst/hookstate-the-modern-extremely-fast-and-extendable-state-management-for-react-that-is-based-on-hooks-4on8</guid>
      <description>&lt;p&gt;Please, meet &lt;a href="https://hookstate.netlify.com/"&gt;Hookstate&lt;/a&gt; - modern alternative to Redux, Mobx, Formik without boilerplate but with impressive performance and predictable behavior. It allowed me to remove Redux and Mobx, and as a result improve the code quality and performance of my projects. It has got very simple API. It is extendable by plugins. And it has got impressive performance: here is the &lt;a href="https://hookstate.netlify.com/performance-demo-large-form"&gt;example of the form state management with 5000 fields&lt;/a&gt; and &lt;a href="https://hookstate.netlify.com/performance-demo-large-table"&gt;the example of the table state with 10000 cells&lt;/a&gt;, where one random cell is updated every millisecond.&lt;/p&gt;

&lt;p&gt;I am interested in to receive the feedback from the community.&lt;/p&gt;

</description>
      <category>react</category>
      <category>typescript</category>
    </item>
  </channel>
</rss>
