Note need to rerun codegen when schema changes (#1050)

docs/generation.rst

@@ -10,7 +10,11 @@ TypeScript/JavaScript.
 To get started with generators, first initialize an :ref:`EdgeDB project
 <ref_guide_using_projects>` in the root of your application. Generators will
 look for an ``edgedb.toml`` file to determine the root of your application. See
-the :ref:`Overview <edgedb-js-installation>` page for details on installing
+the :ref:`Overview <edgedb-js-installation>` page for details on installing.
+
+.. note::
+
+   Generators work by connecting to the database to get information about the current state of the schema. Make sure you run the generators again any time the schema changes so that the generated code is in-sync with the current state of the schema.
 
 Run a generator with the following command.
 

docs/interfaces.rst

@@ -107,8 +107,11 @@ This will introspect your schema and generate TypeScript interfaces that corresp
     actors: Person[];
   }
 
-Any types declared in a non-``default`` module  will be generated into an
-accordingly named ``namespace``.
+Any types declared in a non-``default`` module  will be generated into an accordingly named ``namespace``.
+
+.. note::
+
+   Generators work by connecting to the database to get information about the current state of the schema. Make sure you run the generators again any time the schema changes so that the generated code is in-sync with the current state of the schema.
 
 
 Customize file path

docs/queries.rst

@@ -177,6 +177,10 @@ We can now use this function in our code.
     user.email; // string
   }
 
+.. note::
+
+   Generators work by connecting to the database to get information about the current state of the schema. Make sure you run the generators again any time the schema changes so that the generated code is in-sync with the current state of the schema.
+
 
 Single-file mode
 ----------------
@@ -274,4 +278,4 @@ However, it's better practice to declare it once by assigning it to a variable i
 and reference that variable in the rest of your query. This way you avoid mismatched types in your declarations, 
 such as forgetting to mark them all as `optional </docs/edgeql/parameters#optional-parameters>`__.
 
-Check out the `EdgeQL docs </docs/edgeql/index>`__ to learn more about writing queries. 
+Check out the `EdgeQL docs </docs/edgeql/index>`__ to learn more about writing queries.

docs/querybuilder.rst

@@ -149,6 +149,10 @@ The generator also supports all the :ref:`connection flags
 necessary when using a project or environment variables to configure a
 connection.
 
+.. note::
+
+   Generators work by connecting to the database to get information about the current state of the schema. Make sure you run the generators again any time the schema changes so that the generated code is in-sync with the current state of the schema.
+
 .. _edgedb-js-execution:
 
 Expressions