Add Edge event reference#44
Conversation
Codecov Report
@@ Coverage Diff @@
## dev-v2.0.1 #44 +/- ##
=============================================
Coverage 83.28% 83.28%
Complexity 367 367
=============================================
Files 29 29
Lines 1555 1555
Branches 219 219
=============================================
Hits 1295 1295
Misses 161 161
Partials 99 99
Flags with carried forward coverage won't be shown. Click here to find out more. |
Documentation/event-reference.md
Outdated
| #### Event Details<!-- omit in toc --> | ||
|
|
||
| | Event type | Event source | | ||
| | -------------------------- | ------------------------------------ | |
There was a problem hiding this comment.
We can remove this table since the next table L32 has the same info with the API.
There was a problem hiding this comment.
Thanks for catching that! Removed table
Fix event source value
timkimadobe
left a comment
There was a problem hiding this comment.
Thank you for the review @addb! Updated based on feedback
Documentation/event-reference.md
Outdated
| #### Event Details<!-- omit in toc --> | ||
|
|
||
| | Event type | Event source | | ||
| | -------------------------- | ------------------------------------ | |
There was a problem hiding this comment.
Thanks for catching that! Removed table
Documentation/event-reference.md
Outdated
|
|
||
| | Key | Value type | Required | Description | | ||
| | ------------ | ------------- | -------- | -------------------------- | | ||
| | locationHint | `boolean` | Yes | The Edge Network location hint to use when connecting to Edge Network. Property is set to `true` automatically; it is not user modifiable. | |
There was a problem hiding this comment.
This field is used to distinguish (edge, requestIdentity) event is a getter for locationHint. Let's update the description accordingly.
There was a problem hiding this comment.
We can add Required value as Yes (internal)
There was a problem hiding this comment.
That makes sense! Thank you, updated description section
For the Required column what do you think about updating the column name to Key Required or Mandatory Key? Since this doc is from the perspective of Edge extension's own event contract, all of the "Required"-ness should already be implied to be internal right?
There was a problem hiding this comment.
Makes sense. We can keep it as is then.
Documentation/event-reference.md
Outdated
|
|
||
| This event signals that [Identity for Edge Network](https://github.com/adobe/aepsdk-edgeidentity-android) has completed [resetting all identities](https://developer.adobe.com/client-sdks/documentation/identity-for-edge-network/api-reference/#resetidentities) usually following a call to [`MobileCore.resetIdentities()`](https://github.com/adobe/aepsdk-core-android/blob/main/Documentation/MobileCore/api-reference.md). | ||
|
|
||
| When this event is received, the Edge extension queues it up and removes the cached internal state:store settings. If other events are queued before this event, these events will be processed first in the order they were received. |
There was a problem hiding this comment.
... queued before this event, those events...
Documentation/event-reference.md
Outdated
|
|
||
| This event is a response to the [Edge request identity event](#edge-request-identity)) and provides the location hint being used by the Edge Network extension in requests to the Edge Network. The Edge Network location hint may be used when building the URL for Edge Network requests to hint at the server cluster to use. | ||
|
|
||
| | Value | Behavior | |
There was a problem hiding this comment.
We dont need this consent table here.
There was a problem hiding this comment.
We should add this is dispatched for edge-request-identity event with data containing lochint = true
There was a problem hiding this comment.
Also add a local href to the section getLocHint
There was a problem hiding this comment.
Removed table and added locationHint = true requirement in description
For adding a local href to getLoc Hint, did you mean adding a link to the getLocationHint API in the description for this section? I was thinking the link to Edge request identity event (which has a link to getLocationHint API) would be enough since that API actually creates that event, and not this response one
Documentation/event-reference.md
Outdated
| #### Data payload definition<!-- omit in toc --> | ||
|
|
||
| | Key | Value type | Required | Description | | ||
| | --------- | ------------- | -------- | --------------------- | |
There was a problem hiding this comment.
We can add Required value as Yes (internal)
There was a problem hiding this comment.
Documentation/event-reference.md
Outdated
|
|
||
| | Event type | Event source | | ||
| | --------------------------------- | ------------------------------------- | | ||
| | com.adobe.eventType.edge | This value is copied from the event being responded to; if not set or `null`, has a default value of com.adobe.eventSource.responseContent | |
There was a problem hiding this comment.
just com.adobe.eventSource.responseContent
There was a problem hiding this comment.
I was a bit confused for this one, since the dispatchResponse API is able to generate many different kinds of response events; for this section of "Edge event response" do we only want strictly the
Event type: com.adobe.eventType.edge and Event source: com.adobe.eventSource.responseContent and cover the other potential cases separately in other new sections?
for example dispatchResponse is able to use any eventSource value:
There was a problem hiding this comment.
We should have error response and responseContent. I am not sure how to accommodate any source. @emdobrin @kevinlind Do we have any a limited number eventSource that we expect or this can be anything and we should not try to document each and every known source?
There was a problem hiding this comment.
I've removed the variable event source for now; maybe we can address the variable portion in a followup PR?
Standardize table header formatting for easier find and replace in the future Separate API creating event section Update API signature format to match standard java doc format
timkimadobe
left a comment
There was a problem hiding this comment.
Thanks for the review @addb! Updated based on feedback with a few outstanding questions (attached to relevant feedback comments)
Also, I separated the API column from the table in the cases where the APIs directly create the event into a new section, since if multiple APIs were to create the same event its redundant to repeat the event type/source values for each; what do you think?
Documentation/event-reference.md
Outdated
|
|
||
| | Key | Value type | Required | Description | | ||
| | ------------ | ------------- | -------- | -------------------------- | | ||
| | locationHint | `boolean` | Yes | The Edge Network location hint to use when connecting to Edge Network. Property is set to `true` automatically; it is not user modifiable. | |
There was a problem hiding this comment.
That makes sense! Thank you, updated description section
For the Required column what do you think about updating the column name to Key Required or Mandatory Key? Since this doc is from the perspective of Edge extension's own event contract, all of the "Required"-ness should already be implied to be internal right?
Documentation/event-reference.md
Outdated
|
|
||
| This event signals that [Identity for Edge Network](https://github.com/adobe/aepsdk-edgeidentity-android) has completed [resetting all identities](https://developer.adobe.com/client-sdks/documentation/identity-for-edge-network/api-reference/#resetidentities) usually following a call to [`MobileCore.resetIdentities()`](https://github.com/adobe/aepsdk-core-android/blob/main/Documentation/MobileCore/api-reference.md). | ||
|
|
||
| When this event is received, the Edge extension queues it up and removes the cached internal state:store settings. If other events are queued before this event, these events will be processed first in the order they were received. |
Documentation/event-reference.md
Outdated
|
|
||
| This event is a response to the [Edge request identity event](#edge-request-identity)) and provides the location hint being used by the Edge Network extension in requests to the Edge Network. The Edge Network location hint may be used when building the URL for Edge Network requests to hint at the server cluster to use. | ||
|
|
||
| | Value | Behavior | |
There was a problem hiding this comment.
Removed table and added locationHint = true requirement in description
For adding a local href to getLoc Hint, did you mean adding a link to the getLocationHint API in the description for this section? I was thinking the link to Edge request identity event (which has a link to getLocationHint API) would be enough since that API actually creates that event, and not this response one
Documentation/event-reference.md
Outdated
| #### Data payload definition<!-- omit in toc --> | ||
|
|
||
| | Key | Value type | Required | Description | | ||
| | --------- | ------------- | -------- | --------------------- | |
There was a problem hiding this comment.
Documentation/event-reference.md
Outdated
|
|
||
| | Event type | Event source | | ||
| | --------------------------------- | ------------------------------------- | | ||
| | com.adobe.eventType.edge | This value is copied from the event being responded to; if not set or `null`, has a default value of com.adobe.eventSource.responseContent | |
There was a problem hiding this comment.
I was a bit confused for this one, since the dispatchResponse API is able to generate many different kinds of response events; for this section of "Edge event response" do we only want strictly the
Event type: com.adobe.eventType.edge and Event source: com.adobe.eventSource.responseContent and cover the other potential cases separately in other new sections?
for example dispatchResponse is able to use any eventSource value:
Description
This PR adds the event reference page for the Edge Network extension:
Basically outlining the event contract for all events edge interacts with via the Event Hub
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: