Fix/Support type and status fields in app context #182
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
seba-aln
force-pushed
the
feat/support-type-and-status-fields-in-app-context
branch
from
422891f
to
750a3da
Compare
seba-aln
force-pushed
the
feat/support-type-and-status-fields-in-app-context
branch
from
750a3da
to
a952b67
Compare
seba-aln
changed the title
jguz-pubnub
reviewed
Mar 7, 2024
jguz-pubnub
reviewed
Mar 7, 2024
jguz-pubnub
approved these changes
Mar 7, 2024
seba-aln
force-pushed
the
feat/support-type-and-status-fields-in-app-context
branch
from
73e8090
to
a952b67
Compare
|
@pubnub-release-bot release |
|
🚀 Release successfully completed 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix: Add missing status and type fields in app context. Now they are included, by default, in the response for getting channel/uuid metadata