Skip to content

DOCSP-37027: Fix build errors #1289

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

Merged
merged 13 commits into from
May 10, 2024

Conversation

norareidy
Copy link
Contributor

@norareidy norareidy commented May 7, 2024

@norareidy norareidy requested a review from a team as a code owner May 7, 2024 15:33
@norareidy norareidy requested a review from GromNaN May 7, 2024 15:33
Copy link

@jordan-smith721 jordan-smith721 left a comment

Choose a reason for hiding this comment

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

LGTM!

@@ -27,8 +27,7 @@ Parameters

``$indexName`` : string| :phpclass:`MongoDB\Model\IndexInfo`
The name or model object of the index to drop. View the existing indexes on
the collection using the :phpmethod:`listIndexes()
<MongoDB\Collection::listIndexes>` method.
the collection using the :phpmethod:`MongoDB\Collection::listIndexes()` method.

Choose a reason for hiding this comment

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

Suggested change
the collection using the :phpmethod:`MongoDB\Collection::listIndexes()` method.
the collection by using the :phpmethod:`MongoDB\Collection::listIndexes()` method.

Copy link
Member

@jmikola jmikola left a comment

Choose a reason for hiding this comment

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

No big concerns, although I have a question about extracts-options-requires.yaml.

I noticed this was opened against the master branch. Should it apply further back, or do you plan to manually backport to earlier, deployed branches?

@@ -1,48 +1,43 @@
---
ref: option-requires-4.2
source:
ref: option-requires-version
file: extracts-option-requires.yaml
Copy link
Member

Choose a reason for hiding this comment

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

I was under the impression that both extracts and replacements were supported in Snooty. See slide 49 of Marking up: Tech Writer Training on rST and YAML. Is this not the case, or is there some other limitation here (e.g. a file referencing itself)?

If you're going to remove the inheritance here, I see no reason to preserve the replacement block. The version number might as well just be hard-coded into the content. But before doing that, I would like to address my first question.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok I switched it back to using inheritance - I changed "source:" to "inherit:" and that fixed the build issues. I think that rST / YAML powerpoint might need to be updated, I can investigate why "inherit" fixes the problem.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Never mind, seems like the issue was the missing _ before "option-requires-version"

@@ -29,7 +29,7 @@ Definition
Parameters
----------

``$explainable`` : :phpclass:`MongoDB\Operation\Explainable`
``$explainable`` : ``MongoDB\Operation\Explainable``
Copy link
Member

Choose a reason for hiding this comment

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

Noted that we don't have a stub for the Explainable interface in the docs (nor do we need one), so code formatting is the right call here.

@@ -296,7 +296,7 @@ Parameters
rules or expressions. You can specify the expressions using the same
operators as MongoDB's
:manual:`query operators </reference/operator/query>` with the
exception of :query:`$geoNear`, :query:`$near`, :query:`$nearSphere`,
exception of :query:`$near`, :query:`$nearSphere`,
Copy link
Member

Choose a reason for hiding this comment

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

I assume this dates back to some earlier version of the docs (e.g. 3.2), but I confirmed $geoNear is no longer mentioned in the create docs.

@@ -19,16 +19,15 @@ To get started using in-use encryption in your project, the
to be compiled with `libmongocrypt <https://github.com/mongodb/libmongocrypt>`_
(enabled by default).

Additionally, either `crypt_shared`_ or `mongocryptd`_ are required in order to
Copy link
Member

Choose a reason for hiding this comment

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

I believe these might have been links at some point, which would explain the use of a trailing underscore. In any event, they're no longer defined.

I will point out that this docs page inconsistently uses code-formatting for crypt_shared and mongocryptd. I'm not sure what the server manual does, but we could probably stand to make this internally consistent. Feel free to make this consistent with whatever you do in docs beyond PHPLIB. I also have no objections to just removing all of the backticks for these terms.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Looks like the Server manual formats them in monospace (like on this page), so I monospaced all instances of crypt_shared and mongocryptd

@@ -35,7 +35,7 @@ The bucket can be constructed with various options:
needed. The default size is ``261120`` (i.e. 255 KiB).
- ``readConcern``, ``readPreference`` and ``writeConcern`` options can be used
to specify defaults for read and write operations, much like the
:phpclass:`MongoDB\GridFS\Collection` options.
Copy link
Member

Choose a reason for hiding this comment

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

Good catch.

@norareidy norareidy changed the base branch from master to v1.16 May 7, 2024 17:40
@norareidy norareidy changed the base branch from v1.16 to master May 7, 2024 17:41
@norareidy
Copy link
Contributor Author

No big concerns, although I have a question about extracts-options-requires.yaml.

I noticed this was opened against the master branch. Should it apply further back, or do you plan to manually backport to earlier, deployed branches?

My mistake, I meant to target this against the v1.16 branch. I'll open another PR on that branch.

@norareidy norareidy requested a review from jmikola May 7, 2024 18:34
Copy link
Member

@jmikola jmikola left a comment

Choose a reason for hiding this comment

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

The corresponding v1.16 PR (#1290) is blocked on CI, so let's wait a bit. If we can merge that first (and up to v1.17 and master), it'd be preferable to rebase this down to a smaller diff.

@jmikola jmikola merged commit 783dba8 into mongodb:master May 10, 2024
14 checks passed
@norareidy norareidy deleted the DOCSP-37027-fix-build-issues branch May 10, 2024 14:35
alcaeus added a commit that referenced this pull request May 21, 2024
* v1.19:
  DOCSP-37027: Fix build errors (#1289)
  PHPLIB-1415 Add tests for PHP 8.4 (#1287)
  PHPLIB-1163 Create tutorial for using MongoDB with Bref (#1273)
  Relax branch-alias on dev-master to avoid update on each release (#1277)
  PHPLIB-1424: Fix potentially racy w:0 unified tests (#1276)
  Leverage PHP 8.0 string functions (#1274)
  Master is now 1.19-dev
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants