1. 20 Feb, 2018 1 commit
  2. 17 Feb, 2018 1 commit
  3. 10 Feb, 2018 1 commit
  4. 08 Feb, 2018 4 commits
  5. 07 Feb, 2018 1 commit
  6. 04 Feb, 2018 15 commits
  7. 03 Feb, 2018 1 commit
    • story_result: now use Story AR model · 3cb5b8a4
      Results are now sourced from Postgres, ES is just for search. This is
      better in a lot of ways as we can reduce the amount of data stored in
      ES, and it works quite a bit nicer in Rails.
      
      The source of truth being Postgres means that it's really easy to
      reindex into ES when the schema changes, e.g. for adding relationship
      search.
      Michael Rose authored
  8. 29 Jan, 2018 1 commit
  9. 28 Jan, 2018 2 commits
  10. 26 Nov, 2017 2 commits
  11. 22 Oct, 2017 1 commit
  12. 08 Oct, 2017 1 commit
    • search: Show a helpful error when ES search blows up due to a bad query · d5dafcb7
      Handles Elasticsearch::Transport::Transport::Errors::BadRequest and
      extracts the root cause from the returned error message by parsing it as
      JSON minus the first six characters ('[400]'). This doesn't seem like the
      most robust thing, but wtf -- the JSON is in the error message. Worst case,
      it blows up.
      
      Also redirects back to search index with provided parameters to give the
      user a chance to fix their search.
      Michael Rose authored
  13. 03 Oct, 2017 6 commits
  14. 01 Oct, 2017 2 commits
  15. 30 Sep, 2017 1 commit