Enable Capabilities Vocabulary Configuration

[g2mula]

Issues

Adds support for configuring capabilities vocabulary terms target navigation sources and operations

Description

Configurations are auto generated from the referenced vocabulary model in a default EdmModel.
Extension methods have been added to attach configurations to a navigation source or operation.
A fluent api design has been used for setting configuration properties.

Usage

var modelBuilder = new ODataModelBuilder().Add_Customer_EntityType().Add_Customers_EntitySet();
var entitySetConfiguration = modelBuilder.EntitySet<Customer>("Customers");

var deleteRestrictionsBuilder = entitySetConfiguration
    .HasDeleteRestrictions()
    .IsDeletable(false)
    .HasDescription(Description);

Nested configurations can also be easily added via chaining eg

var operationRestrictionsBuilder = actionConfiguration
    .HasOperationRestrictions()
    .IsFilterSegmentSupported(true)
    .HasPermissions(
        new PermissionTypeConfiguration()
            .HasSchemeName(SchemeName)
            .HasScopes(
                new ScopeTypeConfiguration()
                    .HasScope(CustomerReadWriteAllScope)
                    .HasRestrictedProperties("*")));

Checklist (Uncheck if it is not completed)

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

Additional work

Opened new Task #10 Supporting attributes that can be automatically read by the ConventionModelBuilder.
Opened Docs PR at MicrosoftDocs/OData-docs#141

[g2mula]

The solution looks good to me. @mikepizzo can you leave your comments?
Besides, Do we support "attribute" model builder.

For example, consider:

[DeleteRestriction("Customers", true, .....]
public class Customer
{
....
}

So, developer can use ODataConventionModelBuilder to builder the model with restricitons.

The attrubute modelbuilder is something we can look at in another task, we need to consider the complex nature of some of the options we could want to be able to configure directly in the attribute... If we can come up with clear rules on these, then auto generation of this should also be possible

[xuzhg]

Please file an issue and copy/paste the link into this PR.
Besides, i noticed there are only two test case classes, would you please add more?
In summary, it looks good to me. So i approve it with little comments.

---

In reply to: 655538126 [](ancestors = 655538126)

[xuzhg]

[habbes]

@g2mula could you give an example of how to add navigation restrictions?

The HadNavigationProperty() method requires an IEdmPathExpression parameter. Constructing a new EdmPathExpression instance requires passing the path segments. Here's where I'm not sure what is expected. If, say, I wanted to pass an EntitySetSegment, I would need to specify the IEdmEntitySet. But since the model has not been built yet (because builder.GetEdmModel() has not yet been called)., I don't have access to the eventual entity sets of the model:

customers.HasNavigationRestrictions().HasRestrictedProperties(rp =>
    rp.HasNavigationProperty(new EdmNavigationPropertyPathExpression(new EntitySetSegment(/* what do I pass here? */)))
        .HasReadRestrictions(r =>
            r.HasPermissions(p =>
                p.HasSchemeName("AuthScheme")
                .HasScopes(s => s.HasScope("Customers.ReadByKey").HasRestrictedProperties("*")))));

[g2mula]

Please file an issue and copy/paste the link into this PR.
Besides, i noticed there are only two test case classes, would you please add more?
In summary, it looks good to me. So i approve it with little comments.

In reply to: 655538126 [](ancestors = 655538126)

Added #10