@bottlebooks/valid-values 1.2.0 → 1.2.1

package/src/validValues/types/ValidValueDefinition.ts

@@ -12,7 +12,7 @@ export interface ValidValueDefinition {
    *
    * Define it using `defineMessage()` from @lingui/macro.
    */
-  title?: string | MessageDescriptor;
+  title: string | MessageDescriptor;
   /**
    * Fields that will never be stored in the database,
    * because they are not relevant to the frontend rendering.

package/dist/validValues/types/Country.js

@@ -1,5 +0,0 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});

package/src/validValues/types/Country.ts

@@ -1,39 +0,0 @@
-import type { MessageDescriptor } from '@lingui/core';
-interface ValidValueEnabledFor {
-  field: string;
-  value: string;
-}
-
-export interface Country {
-  key: string;
-  enabledFor?: ValidValueEnabledFor[];
-  /**
-   * The translatable title of the valid value.
-   *
-   * Define it using `defineMessage()` from @lingui/macro.
-   */
-  title?: string | MessageDescriptor;
-  /**
-   * Fields that will never be stored in the database,
-   * because they are not relevant to the frontend rendering.
-   * They are only used for the form, like grouping values for easier entry.
-   */
-  form?: {
-    /**
-     * A helpful description shown only when using the form.
-     */
-    // description?: MessageDescriptor;
-  };
-  regions?: string[];
-  /**
-   * Fields that are stored in the database together with each lookup value,
-   * because they affect the frontend rendering.
-   * They are also included in the hash values to detect breaking changes.
-   *
-   * We should try to avoid them if possible because if false positives:
-   * Any change in one of those fields would lead to
-   * eLabels that are marked as incompatible,
-   * although there might be no user-visible changes.
-   */
-  frontend?: {};
-}