We current have a "dependency resolution" system for Produces and Consumes declarations. This is based on best intent that the declarations matches the implementation. Today, there is nothing prevents a producer/consumer to declare DataKey-X but actually produce/consume DataKey-Y.
One possible solution to only expose the Put/Get via the DataKey itself, so the publisher/consumer can only use the declared DataKeys to access the AttributeMap.
cc @rahulgurnani
We current have a "dependency resolution" system for
ProducesandConsumesdeclarations. This is based on best intent that the declarations matches the implementation. Today, there is nothing prevents a producer/consumer to declareDataKey-Xbut actually produce/consumeDataKey-Y.One possible solution to only expose the
Put/Getvia theDataKeyitself, so the publisher/consumer can only use the declared DataKeys to access the AttributeMap.cc @rahulgurnani