Skip to content

reevaluate which fields need to be required #76

@hanastasov

Description

@hanastasov

#70 marks the fields under Address as required.

This breaks UX, as each AB user cant do a quick demo or anything, because a fields like address.region is required. which does not follow any business rule. At the same time, we need the NW to be easy for demos and so many required fields compromise this.

  1. Revert Add Require attribute tofields in AddressDto #70
  2. Also think about other required fields that may be converted to optoonal

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions