Skip to content

defaultValues on fields that are not optional #81

@sirganya

Description

@sirganya

This code fails the validation when the key is left out. I was using simple schema and attaching it to collections originally. I'd like to migrate to validatedMethod. Any strategies to combine the two that work? I have simple schema setting a lot of defaults throughout the app..

eurPrice: {
    type: String,
    regEx: /(?=.*\d)^\$?(([1-9]\d{0,2}(,\d{3})*)|0)?(\.\d{1,2})?$/,
    label: 'EUR Price',
    defaultValue: '0',
  },

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions