Capabilities | Serverpod The basics | Serverpod Custom overrides | Serverpod Apple | Serverpod Custom providers | Serverpod Email | Serverpod Firebase | Serverpod Google | Serverpod Setup | Serverpod Working with users | Serverpod Backward compatibility | Serverpod Caching | Serverpod Configurations | Serverpod Connection | Serverpod CRUD | Serverpod Filter | Serverpod Indexing | Serverpod Migrations | Serverpod Models | Serverpod Pagination | Serverpod Raw access | Serverpod Relation queries | Serverpod Many-to-many | Serverpod Relations with modules | Serverpod One-to-many | Serverpod One-to-one | Serverpod Referential actions | Serverpod Self-relations | Serverpod Sort | Serverpod Transactions | Serverpod Error handling and exceptions | Serverpod Experimental features | Serverpod Uploading files | Serverpod Health checks | Serverpod Logging | Serverpod Working with models | Serverpod Modules | Serverpod Scheduling | Serverpod Custom serialization | Serverpod Server events | Serverpod Sessions | Serverpod Streams | Serverpod Advanced examples | Serverpod Best practises | Serverpod Get started | Serverpod The basics | Serverpod Web server | Serverpod Working with endpoints | Serverpod Roadmap & contributions | Serverpod Community-supported deployments | Serverpod AWS EC2 with Terraform | Serverpod Google Cloud Engine with Terraform | Serverpod Google Cloud Run with CGP Console | Serverpod Choosing deployment strategy | Serverpod Hosting elsewhere | Serverpod Get started with Mini | Serverpod Get started | Serverpod Installing Serverpod | Serverpod Installing Serverpod | Serverpod Capabilities | Serverpod The basics | Serverpod Custom overrides | Serverpod Apple | Serverpod Custom providers | Serverpod Email | Serverpod Firebase | Serverpod Google | Serverpod Setup | Serverpod Working with users | Serverpod Backward compatibility | Serverpod Caching | Serverpod Configurations | Serverpod Connection | Serverpod CRUD | Serverpod Filter | Serverpod Indexing | Serverpod Migrations | Serverpod Models | Serverpod Pagination | Serverpod Raw access | Serverpod Relation queries | Serverpod Many-to-many | Serverpod Relations with modules | Serverpod One-to-many | Serverpod One-to-one | Serverpod Referential actions | Serverpod Self-relations | Serverpod Sort | Serverpod Transactions | Serverpod Error handling and exceptions | Serverpod Experimental features | Serverpod Uploading files | Serverpod Health checks | Serverpod Logging | Serverpod Working with models | Serverpod Run serverpod generate to generate dart classes from the model files.
Class
class : Company fields : name : String foundedDate : DateTime ? employees : List<Employee > Supported types are bool , int , double , String , Duration , DateTime , ByteData , UuidValue , and other serializable classes , exceptions and enums . You can also use List s and Map s of the supported types, just make sure to specify the types. Null safety is supported. Once your classes are generated, you can use them as parameters or return types to endpoint methods.
+Supported types are bool , int , double , String , Duration , DateTime , ByteData , UuidValue , Uri , BigInt and other serializable classes , exceptions and enums . You can also use List s, Map s and Set s of the supported types, just make sure to specify the types. Null safety is supported. Once your classes are generated, you can use them as parameters or return types to endpoint methods.
Limiting visibility of a generated class
By default, generated code for your serializable objects is available both on the server and the client. You may want to have the code on the server side only. E.g., if the serializable object is connected to a database table containing private information.
To make a serializable class generated only on the server side, set the serverOnly property to true.
diff --git a/docs/next/concepts/modules.html b/docs/next/concepts/modules.html
index e61f7b55d..b944f59d5 100644
--- a/docs/next/concepts/modules.html
+++ b/docs/next/concepts/modules.html
@@ -4,7 +4,7 @@
Modules | Serverpod Scheduling | Serverpod Security Configuration | Serverpod Custom serialization | Serverpod Server events | Serverpod Sessions | Serverpod Streams | Serverpod Advanced examples | Serverpod Best practises | Serverpod Get started | Serverpod The basics | Serverpod Web server | Serverpod Working with endpoints | Serverpod apiServer : port : 8080 publicHost : localhost publicPort : 8080 publicScheme : http ... You can pass the --watch flag to serverpod generate to watch for changed files and generate code whenever your source files are updated. This is useful during the development of your server.
Passing parameters
-There are some limitations to how endpoint methods can be implemented. Parameters and return types can be of type bool, int, double, String, UuidValue, Duration, DateTime, ByteData, or generated serializable objects (see next section). A typed Future should always be returned. Null safety is supported. When passing a DateTime it is always converted to UTC.
-You can also pass List and Map as parameters, but they need to be strictly typed with one of the types mentioned above. For Map, the keys must be non-nullable strings. E.g., Map<String, int?> is valid, but Map<int, String> is not.
+There are some limitations to how endpoint methods can be implemented. Parameters and return types can be of type bool, int, double, String, UuidValue, Duration, DateTime, ByteData, Uri, BigInt, or generated serializable objects (see next section). A typed Future should always be returned. Null safety is supported. When passing a DateTime it is always converted to UTC.
+You can also pass List, Map, Record and Set as parameters, but they need to be strictly typed with one of the types mentioned above.
While it's possible to pass binary data through a method call and ByteData, it is not the most efficient way to transfer large files. See our file upload interface. The size of a call is by default limited to 512 kB. It's possible to change by adding the maxRequestSize to your config files. E.g., this will double the request size to 1 MB:
Return types
The return type must be a typed Future. Supported return types are the same as for parameters.
diff --git a/docs/next/contribute.html b/docs/next/contribute.html
index 7743759ae..9a0668cf0 100644
--- a/docs/next/contribute.html
+++ b/docs/next/contribute.html
@@ -4,7 +4,7 @@
Roadmap & contributions | Serverpod Community-supported deployments | Serverpod AWS EC2 with Terraform | Serverpod Google Cloud Engine with Terraform | Serverpod Google Cloud Run with CGP Console | Serverpod Choosing deployment strategy | Serverpod Hosting elsewhere | Serverpod Get started with Mini | Serverpod Get started | Serverpod Support & community | Serverpod Serverpod Insights | Serverpod LSP server | Serverpod Authentication | Serverpod Code examples | Serverpod Build your first app | Serverpod Real-time communication | Serverpod Upgrade from Mini to full | Serverpod Upgrade to 1.2 | Serverpod Upgrade to 2.2 | Serverpod Upgrade to 2.0 | Serverpod Support & community | Serverpod Serverpod Insights | Serverpod LSP server | Serverpod Authentication | Serverpod Code examples | Serverpod Build your first app | Serverpod Real-time communication | Serverpod Upgrade from Mini to full | Serverpod Upgrade to 1.2 | Serverpod Upgrade to 2.2 | Serverpod Upgrade to 2.0 | Serverpod