Skip to content

DOCSP-28250-key-handling-button#258

Merged
gmiller-mdb merged 3 commits intomongodb:masterfrom
gmiller-mdb:DOCSP-28250-key-handling-button
Jun 11, 2025
Merged

DOCSP-28250-key-handling-button#258
gmiller-mdb merged 3 commits intomongodb:masterfrom
gmiller-mdb:DOCSP-28250-key-handling-button

Conversation

@gmiller-mdb
Copy link
Collaborator

@gmiller-mdb gmiller-mdb commented Jun 4, 2025

DESCRIPTION

Add information about new key handling button.

STAGING

https://deploy-preview-258--docs-relational-migrator.netlify.app/mapping-rules/create-rules/

https://deploy-preview-258--docs-relational-migrator.netlify.app/mapping-rules/mapping-rule-options/new-documents/

JIRA

https://jira.mongodb.org/browse/DOCSP-28250

BUILD LOG

Self-Review Checklist

  • Is this free of any warnings or errors in the RST?
  • Is this free of spelling errors?
  • Is this free of grammatical errors?
  • Is this free of staging / rendering issues?
  • Are all the links working?

External Review Requirements

What's expected of an external reviewer?

@netlify
Copy link

netlify bot commented Jun 4, 2025

Deploy Preview for docs-relational-migrator ready!

Name Link
🔨 Latest commit f335217
🔍 Latest deploy log https://app.netlify.com/projects/docs-relational-migrator/deploys/6849916d4accd8000897ac64
😎 Deploy Preview https://deploy-preview-258--docs-relational-migrator.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 47 (🔴 down 33 from production)
Accessibility: 92 (🔴 down 6 from production)
Best Practices: 92 (no change from production)
SEO: 92 (no change from production)
PWA: -
View the detailed breakdown and full score reports

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

Copy link
Collaborator

@kennethdyer kennethdyer left a comment

Choose a reason for hiding this comment

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

Thanks @gmiller-mdb, LGTM!

- Change the key handling strategy.

Modify the key handling strategy by clicking the :icon-fa5:`key` icon in
the field panel.

Choose a reason for hiding this comment

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

There are a few expansions I think would be important to make here:

  • The default key strategy is 'autogenerated'. We have docs here which explain each key handling strategy which may be helpful to link to.
  • Changing the key handling strategy changes it for the entire project. Having it in this section makes it seem like you can change it for a specific collection when you can't.
  • Selecting a different key handling strategy is reflected immediately in the project. So if you've edited any keys in any collection those changes may be lost by changing the key strategy.

Let me know if I can clarify anything!

Copy link

@marian-derias marian-derias left a comment

Choose a reason for hiding this comment

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

Good wording, thank you! I do have one suggestion- but this has been sitting for a while so I don't want to block you.

- Change field names.
- To include or exclude a field from your migration job, click the
:icon-fa5:`check-square` icon next to the field name.
- Change the key handling strategy.

Choose a reason for hiding this comment

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

Should this be moved into a different section too because it's not specific to a mapping rule? I'm not familiar with this page- up to you where it should be.

@gmiller-mdb gmiller-mdb merged commit 4350452 into mongodb:master Jun 11, 2025
5 checks passed
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