As the title says. Tested locally by creating a cost report, updating it, getting it to see the updated data, and then deleting it

COMPLETES ENG-1765, ENG-1827, ENG-1828

Fills in the missing folder tools

Tested locally - created a new folder, updated the title, fetched the information about it, and then deleted it.

COMPLETES ENG-1772, ENG-1841, ENG-1842, ENG-1843

Adding some info on publishing practices and bumping the version to include new Anomaly data

Handful of tools for Anomalies. Tested locally that I can fetch an Anomaly and update it's status

COMPLETES ENG-1797, ENG-1799

Move to V4 to keep up to date

What Changed?

I added

• #build_truncate_statements - Update the functionality to filter out engines that cannot be truncated
• Added unit test to ensure functionality
• Added clickhouse/minitest.rb as a helper similar to clickhouse/rspec.rb

Motivation

In our production app we're using database_cleaner to do the truncation and taking advantage of it's except functionality (DatabaseCleaner.strategy = [:truncation, except: %w[widgets]]) to filter out specific tables. I'm hoping to remove our dependency on database_cleaner and allow clickhouse-activerecord to manage the truncation.

The pattern used here follows the ActiveRecord implementation. We currently rely on the abstract implementation for #truncate and #truncate_tables - active_record/connection_adapters/abstract/database_statements.rb.

Postgres and Sqlite use this same pattern to adjust their truncation methods

• postgresql/database_statements.rb - Overrides build_truncate_statements to truncate all tables in a single statement
• sqlite3/database_statements.rb - Overrides build_truncate_statement to use DELETE FROM since SQLite doesn't support TRUNCATE

Related to vantage-sh/core#13141

This test fails against master without the above PR merged in. With the changes, this test passes.

COMPLETES ENG-466

zbugs: Potential for a better error message when a table is referenced in a relationship but not included in createSchema

Thank you @arv for the work on #3477. It pointed me in the direction of where to look code wise. I wanted to expand the work that was done to resolve the issue I ran into where defining a destSchema for a table that isn't referenced in schema.tables causes an error.

I added test cases for two potential ways to have a missing table. If anyone can think of other scenarios I can gladly write more tests.

My only question about adding this, while I think it improves the DX and will help people to ensure their schema is valid, is there any concern about runtime cost and having createSchema doing this additional work?

I was trying to use bright to highlight the gleam language. Everything was in place in tm-grammars to do that, bright just needed to be able to access the newer languages. Updating to the latest release of lighter gives us access to the newer version of tm-grammars.

I'm not super familiar with lighter, but it also has a pinned exact version of tm-grammars, currently set to "1.16.2". It may be a good idea to relax that requirement so that new languages that get added can be accessed without having to publish newer versions.

Fixes: #203

Preface: This is my first exposure to working with these Node objects on the server side so I'm not entirely sure if what I've done is correct.

I changed the way the incremental responses are sent back to the client. In the issue I noted

      for await (const chunk of httpGraphQLResponse.body.asyncIterator) {
        body.push(chunk);
      }

this await is stopping the server from incrementally delivering the responses and instead they're all delivered at once.

These changes allow the responses to be streamed back instead of all at once.

The logs in the client now show

what is data? {book: {…}} false 12:22:18
what is data? {book: {…}} false 12:22:19

Where the second book: {} has the deferred data and is delivered 1 second after the first in which the 1 second is hard coded in my project using this package.