Skip to content

New API to populate raw Common Schema 4.0 fields #1

Description

There are several fields that cannot be currently populated by SDK. Example:

  • ext.app.env
  • ext.container
  • etc.

Feature request:

  • add new CS4.0 fields definition and regenerate the C++ bond-related code
  • introduce a generic schema mapping mechanism that would allow to expose any new CS protocol field via SetProperty and SetContext API to the app caller

Request comes from MS Edge team.

Activity

  1. maxgolov commented on Jun 18, 2019

    @maxgolov
    ContributorAuthor

    This is also identical to MS Edge team ask "CS 3.0: Need a general method for updating all CS 3.0 optional fields." tracked under Task 22164965.

  2. maxgolov commented on Oct 4, 2019

    @maxgolov
    ContributorAuthor

    As discussed in several other threads: currently there is no more practical need to add more semantic APIs for individual common schema fields. Instead there's a new custom decorator pattern that allows to efficiently adjust the raw Common Schema Protocol Record fields. Customers who know they use Common Schema, and need to set specific schema field value - can use this pattern to populate the fields.

    Example:

    class CustomDecorator: public IDecoratorModule

    I'm closing this issue in favor a custom decorator concept suggested above.

  3. added a commit that references this issue on Nov 5, 2019
  4. added a commit that references this issue on Oct 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

EDGEPartner Team - Microsoft EdgeenhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions