Key Alias support

[ElizabethOkerio]

Issues

This pull request fixes #xxx.

Key Alias support in ODL Here's an example for Key alias:

"Category": {
  "$Kind": "EntityType",
  "$Key": [
    {
      "EntityInfoID": "Info/ID"
    }
  ],
  "Info": {
    "$Type": "self.EntityInfo"
  },
  "Name": {
    "$Nullable": true
  }
},
"EntityInfo": {
  "$Kind": "ComplexType",
  "ID": {
    "$Type": "Edm.Int32"
  },
  "Created": {
    "$Type": "Edm.DateTimeOffset",
    "$Precision": 0
  }
}

EntityInfoID is the alias and Info/ID is the path to the key.

Changes made in this PR: New interfaces and Classes;

1. IEdmStructuralPropertyAlias : IEdmStructuralProperty - this interface has two properties: - IEnumerable Path { get; } and string PropertyAlias { get; }
2. EdmStructuralPropertyAlias : EdmProperty, IEdmStructuralPropertyAlias

EdmStructuredType Added a new method public EdmStructuralPropertyAlias AddStructuralPropertyAlias(IEdmTypeReference type, string alias, IEnumerable path) - This is the method that users will use to add key aliases.

1. type is the type of the complex property
2. alias is the key alias to use
3. path is a list of the path segments to the key property.

EdmEntityType In the AddKeys(IEnumerable<IEdmStructuralProperty> keyProperties) method, when looping through each property, we cast it into an IEdmStructuralPropertyAlias and check if the key has an alias or not. If it does, we loop through the keyProperties till we get to the last path segment which is the key and create an EdmStructuralPropertyAlias and add it to the declaredKeys IEnumerable.

Description

Briefly describe the changes of this pull request.

Checklist (Uncheck if it is not completed)

• [ ] Test cases added
• [ ] 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.

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

This PR has 372 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       : +356 -16
Percentile : 77.2%

Total files changed: 17

Change summary by file extension:
.cs : +326 -16
.bsl : +30 -0

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 detetcted.
• 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.

[xuzhg]

@ElizabethOkerio Let's kick it off again:

here's my thought:

Basically, we can add a new interface:

    public interface IEdmPropertyRef: IEdmNamedElement
    {
        IEdmProperty Property { get; set; }

        string Path { get; set; }  // or IEdmPathExpression

        string Alias { get; set; }
    }

So, change:

public class EdmEntityType
{
-       private List<IEdmStructuralProperty> declaredKey;
+       private List<IEdmPropertyRef> declaredKey;

+       public void AddKeys(params IEdmPropertyRef[] keyProperties)
+       {}

+       public void AddKeys(params IEdmPropertyRef[] keyProperties)
+       {}
}

Change the existing AddKeys, and add others.