@plutocms/pluto 0.9.0 → 0.10.0

package/CHANGELOG.md

@@ -1,6 +1,20 @@
 # Changelog
 
 
+## [0.10.0](https://github.com/plutocms/pluto/compare/v0.9.1...v0.10.0) (2026-09-13)
+
+
+### Features
+
+* **content:** add virtual field flag for column-less content-type fields ([#143](https://github.com/plutocms/pluto/issues/143)) ([cf9091e](https://github.com/plutocms/pluto/commit/cf9091e57d21520d92197ba562eef073ef469ee1))
+
+## [0.9.1](https://github.com/plutocms/pluto/compare/v0.9.0...v0.9.1) (2026-09-13)
+
+
+### Bug Fixes
+
+* **content:** import content types explicitly instead of relying on auto-import ([#141](https://github.com/plutocms/pluto/issues/141)) ([57bd5ab](https://github.com/plutocms/pluto/commit/57bd5ab7d8c9c4748fe679196a0ed08222040082))
+
 ## [0.9.0](https://github.com/plutocms/pluto/compare/v0.8.1...v0.9.0) (2026-09-13)
 
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@plutocms/pluto",
   "type": "module",
-  "version": "0.9.0",
+  "version": "0.10.0",
   "description": "The layerable CMS",
   "author": "Victor Ribeiro",
   "license": "MIT",

package/shared/types/content.ts

@@ -25,6 +25,8 @@ export interface PlutoFieldBase {
   description?: string
   /** Storage column, when it differs from `name`. Falls back to `name` when unset. */
   column?: string
+  /** This field has no storage column. Its value never reaches `mapFieldsToColumns`'s output, but still passes through validation and the generic form payload — letting a `hooks.afterCreate`/`afterUpdate` read it from `rawBody` without a matching database column. */
+  virtual?: boolean
   required?: boolean
   /** Show this field as a column in the generic list view. Default false. */
   inList?: boolean

package/shared/utils/content-map.ts

@@ -1,3 +1,5 @@
+import type { PlutoContentItem, PlutoContentType, PlutoField } from '../types/content'
+
 /** Resolves the storage column for a field. Falls back to `field.name` when `field.column` is unset. */
 export function fieldColumn(field: PlutoField): string {
   return field.column ?? field.name
@@ -9,6 +11,9 @@ export function fieldColumn(field: PlutoField): string {
  * left out of the result, so a partial update payload stays partial after
  * mapping. An adapter (a later wave) sends the result straight to its
  * storage layer.
+ *
+ * A field with `virtual: true` never appears in the result, even when
+ * `payload` has a value for it — it has no storage column by design.
  */
 export function mapFieldsToColumns(
   type: PlutoContentType,
@@ -17,6 +22,9 @@ export function mapFieldsToColumns(
   const columns: Record<string, unknown> = {}
 
   for (const field of type.fields) {
+    if (field.virtual) {
+      continue
+    }
     if (Object.hasOwn(payload, field.name)) {
       columns[fieldColumn(field)] = payload[field.name]
     }
@@ -30,6 +38,11 @@ export function mapFieldsToColumns(
  * every field in `type.fields`, plus the primary key column (`type.primaryKey`,
  * default `'id'`) mapped to `item.id`. A column absent from `row` is left
  * out of the result field.
+ *
+ * A field with `virtual: true` is skipped, for symmetry with
+ * `mapFieldsToColumns` — it has no column to read back from `row` in the
+ * first place, so this only guards against a stray column that happens to
+ * share the field's name.
  */
 export function mapColumnsToFields(
   type: PlutoContentType,
@@ -39,6 +52,9 @@ export function mapColumnsToFields(
   const item: Record<string, unknown> = { id: row[primaryKey] }
 
   for (const field of type.fields) {
+    if (field.virtual) {
+      continue
+    }
     const column = fieldColumn(field)
     if (Object.hasOwn(row, column)) {
       item[field.name] = row[column]

package/shared/utils/content-validate.ts

@@ -1,3 +1,5 @@
+import type { PlutoContentType } from '../types/content'
+
 export interface ContentValidationError {
   field: string
   message: string

package/shared/utils/content.ts

@@ -1,3 +1,5 @@
+import type { PlutoContentType } from '../types/content'
+
 /**
  * Declares a content type. This is an identity function: it returns `type`
  * unchanged. Its only job is type inference at the call site — wrapping a