Support optional facets on type definitions

[gathogojr]

Issues

This pull request fixes #2246.

Description

This pull request is a follow up to https://github.com/OData/odata.net/pull/2779. It implements support for facets that appear on type definitions. For example,

<TypeDefinition Name="SimpleIdentifier" UnderlyingType="Edm.String" MaxLength="128">
  <Annotation Term="Core.Description" String="A [simple identifier](https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_SimpleIdentifier)" />
  <Annotation Term="Validation.Pattern" String="^[\p{L}\p{Nl}_][\p{L}\p{Nl}\p{Nd}\p{Mn}\p{Mc}\p{Pc}\p{Cf}]{0,}$" />
</TypeDefinition>

Notes:

• Currently, when a string property doesn't specify a Unicode facet, a default value of true is implied. For the same reason, when serializing an string property, we currently don't write the Unicode facet if the value is true or null. However, when it comes to a Unicode facet specified on a type definition, we should be explicit when serializing the type definition, i.e., write the Unicode facet if the value is true. This is because elements that use a type definition MUST NOT re-specify any facet specified on the type definition. Reading and writing the facet as explicitly specified makes it easy to validate this restriction.
• For same reasoning as above, we explicitly write the spatial reference system identifier (SRID) value for Geometry and Geography properties where their default values (0 and 4326 respectively) are explicitly specified on a type definition.

Checklist (Uncheck if it is not completed)

• [x] Test cases added
• [x] Build and test with one-click build and test script passed

Additional work necessary

If documentation update is needed, please add "Docs Needed" label to the issue and provide details about the required document change in the issue.

[gathogojr]

Should this feature also be supported in CSDL JSON?

@habbes Good catch. Made the relevant changes to ensure the facets get serialized for CSDL/JSON. The CSDL parser currently doesn't support deserializing CSDL/JSON.

[pull-request-quantifier-deprecated[bot]]

This PR has 303 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Large
Size       : +297 -6
Percentile : 70.3%

Total files changed: 14

Change summary by file extension:
.cs : +296 -5
.xml : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.