Fider
Sunday, March 25, 2018

Fider 0.11 released with option to edit and delete ideas

Introduction

It's very well known that as the size of the codebase grows, so does the complexity and time needed to maintain it. This is a common characteristic of most software programs and thus, not different for Fider.

As we evolve one version a month we need to always look back and improve older code, even those small pieces that are still working sometimes needs some love. Refactoring older code to make it easier to read, maintain and change is something we'll be doing more often moving forward. We want Fider to be a place where anyone with any skill level can join, change, extend and improve it.

Starting today on all new release blog posts, we'll list some (or even all) other activities that have been done, which usually relates to refactoring, tooling changes, bug fixes and enhancements.

#1: Delete Ideas

Administrators are now able to delete ideas that are not yet closed yet. This is specifically useful to remove spam / off-topic ideas. Although it can be used to remove duplicate ideas, we recommend the usage of Duplicate status as transfers vote to the original idea.

#2: Edit Comments

Comment authors can now edit their own comments to fix typos or include any missing information. Administrators are also able to edit all comments on their site. Once a comment has been edited, a small comment is show beside the original comment date.

Other Changes on Fider 0.11

  • enhancement: tie up all tables with tenant_id (#279)
  • refactoring: removed jQuery (#171)
  • refactoring: react naming convention and folder structure (#276)
  • refactoring: internal changes that requires less SQL queries to run (#281, #277, #280)
  • tooling: add Prettier (#309) thanks to @LukeSheard
  • tooling: update JS & Go dependencies (#273)
  • fix: goroutine Leak (#286)
  • fix: race condition on worker process (#313)
  • docs: Review Fider contributing process, files, templates (#278)

What's next?

Help us shape the future of Fider. Visit our feedback forum and raise your voice. Tell us what to do next.