DOP-6197: preserve hash when hash not within composable #1566
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.
Stories/Links:
This is part 2 of the fix applied to DOP-6197
Previous PR addressed when hash was within the composable, but original case was for a hash below the composable tutorial. (see content here)
Current Behavior:
Behavior in prod (note stripped hash and not landing correctly):
https://www.mongodb.com/docs/atlas/atlas-search/about/feature-compatibility/#supported-clients
Testing link in staging / qa (same result):
https://mongodbcom-cdn.staging.corp.mongodb.com/docs/atlas/atlas-search/about/feature-compatibility/#supported-clients
Previous fix applied in staging/prod - this only applied to content with composable tutorials:
http://mongodb.com/docs/atlas/atlas-search/tutorial/#create-the--index.-18
https://mongodbcom-cdn.staging.corp.mongodb.com//docs/atlas/atlas-search/tutorial/#create-the--index.-18
Staging Links:
Testing link on my branch
Put a link to your staging environment(s), if applicable
Notes:
README updates