DOCSP-45200: Change streams

[norareidy]

Pull Request Info

PR Reviewing Guidelines

JIRA - https://jira.mongodb.org/browse/DOCSP-45200

Staging Links

read/change-streams

read

Self-Review Checklist

• Is this free of any warnings or errors in the RST?
• Did you run a spell-check?
• Did you run a grammar-check?
• Are all the links working?
• Are the facets and meta keywords accurate?

[netlify]

✅ Deploy Preview for docs-ruby ready!

Name	Link
🔨 Latest commit	7b68ed7
🔍 Latest deploy log	https://app.netlify.com/sites/docs-ruby/deploys/678aa50389ea930008f03e94
😎 Deploy Preview	https://deploy-preview-123--docs-ruby.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[rachel-mack]

LGTM

[jamis]

Using stream#each will be simpler, and more idiomatic:

Suggested change

	enum = stream.to_enum
	while (doc = enum.next)
	puts doc
	break if doc['operationType'] == 'invalidate'
	end
	stream.each do |doc|
	puts doc
	break if doc['operationType'] == 'invalidate'
	end

[jamis]

Explicitly converting the stream to an enum is usually a hint that you're doing something the hard way. Prefer stream#each when iterating over a stream:

Suggested change

	enum = stream.to_enum
	while (doc = enum.next)
	puts doc
	break if doc['operationType'] == 'invalidate'
	end
	stream.each do |doc|
	puts doc
	break if doc['operationType'] == 'invalidate'
	end

[jamis]

Suggested change

	enum = stream.to_enum
	while (doc = enum.next)
	puts doc
	break if doc['operationType'] == 'invalidate'
	end
	stream.each do |doc|
	puts doc
	break if doc['operationType'] == 'invalidate'
	end

[jamis]

There's no need to convert the change stream to an enumerator, as the stream is already iterable. Maybe something like the following?

Suggested change

	When using the {+driver-short+}, you can call the ``watch`` method to return a
	``Mongo::Collection::View::ChangeStream`` object. Then, you can convert the change
	stream to an ``Enumerator`` object and iterate through its content to monitor data
	changes, such as updates, insertions, and deletions.
	When using the {+driver-short+}, you can call the ``watch`` method to return a
	``Mongo::Collection::View::ChangeStream`` object. Then, you can iterate through
	its content to monitor data changes, such as updates, insertions, and deletions.

[norareidy]

I like this wording, updated! Sorry about that confusion

[jamis]

As mentioned, there's no need to convert the stream to an enumerator.

Suggested change

	The following example opens a change stream on the ``restaurants`` collection,
	converts the change stream to an ``Enumerator``, and outputs changes as they occur:
	The following example opens a change stream on the ``restaurants`` collection
	and outputs changes as they occur: