Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add fetch messages and custom message type support #165

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

parfeon
Copy link
Contributor

@parfeon parfeon commented Dec 10, 2024

feat(history): add batch history support

Add fetch messages (batch history) endpoint support to fetch history for multiple channels.

feat(history): add fetch messages with message reactions

Add fetch messages with reactions support.

feat(custom-message-type): add support for fetch messages

Add include_custom_message_type support for fetch messages endpoint.

feat(custom-message-type): add support for publish and subscribe

Add custom_message_type support for publish / signal and subscribe endpoints.

Add `custom_message_type` support for publish / signal and subscribe endpoints.
@parfeon parfeon added status: done This issue is considered resolved. priority: medium This PR should be reviewed after all high priority PRs. type: feature This PR contains new feature. labels Dec 10, 2024
@parfeon parfeon self-assigned this Dec 10, 2024
@parfeon parfeon requested a review from seba-aln as a code owner December 10, 2024 12:49
Add fetch messages (batch history) endpoint support to fetch history for multiple channels.

feat(history): add fetch messages with message reactions

Add fetch messages with reactions support.

feat(custom-message-type): add support for fetch messages

Add `include_custom_message_type` support for fetch messages endpoint.
@parfeon parfeon changed the title Add support for publish and subscribe Add fetch messages and custom message type support Jan 2, 2025
Copy link
Contributor

@seba-aln seba-aln left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@@ -65,14 +65,14 @@ def send_request(compressed_body = '', header = {})

begin
@app.record_telemetry(@telemetry_name, telemetry_time_start, ::Time.now.to_f)
rescue StandardError => error
Pubnub.logger.warn('Pubnub::Event') { "Couldn't record telemetry because of #{error}\n#{error.backtrace.join("\n")}" }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume the rename was to fit in line length limit. error name was better, but I understand ;)

end
end

it "__channel__demo3___max__5__start__nil___end__nil___include_uuid__false___include_meta__false___include_message_actions__false___include_message_type__false___include_custom_message_type__false__http_sync__true___callback__nil___encrypted__true___random_iv__true_" do
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what.
the.
hell.
??

random_iv = options.key?(:random_iv) ? options[:random_iv] : true
options[:crypto_module] = Crypto::CryptoModule.new_legacy(options[:cipher_key], random_iv) if options[:cipher_key]

super
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

super :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: medium This PR should be reviewed after all high priority PRs. status: done This issue is considered resolved. type: feature This PR contains new feature.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants