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

Migrating from util::Optional to std::optional since Realm Core is moving that way #6449

Merged
merged 5 commits into from
Feb 9, 2024

Conversation

kneth
Copy link
Contributor

@kneth kneth commented Jan 30, 2024

What, How & Why?

The Realm Core team wishes to stop using util::Optional and start using std::optional. Currently util::Optional is an alias but will eventually disappear. Together with realm/realm-core#7284 we are preparing for the future.

Not sure why package-lock.json needs to be updated.

☑️ ToDos

  • 📝 Changelog entry
  • 📝 Compatibility label is updated or copied from previous entry
  • 📝 Update COMPATIBILITY.md
  • 🚦 Tests
  • 📦 Updated internal package version in consuming package.jsons (if updating internal packages)
  • 📱 Check the React Native/other sample apps work if necessary
  • 💥 Breaking label has been applied or is not necessary

@cla-bot cla-bot bot added the cla: yes label Jan 30, 2024
@kneth kneth requested a review from elle-j January 30, 2024 14:05
@kneth kneth requested a review from kraenhansen January 30, 2024 14:05
@kneth kneth changed the title Migrating from tul::Optional to std::optional since Realm Core is moving that way Migrating from util::Optional to std::optional since Realm Core is moving that way Jan 30, 2024
Copy link

Coverage Status

coverage: 85.346%. remained the same
when pulling 3ca0cf4 on kneth/optional
into 474e395 on main.

CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Contributor

@elle-j elle-j left a comment

Choose a reason for hiding this comment

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

Future, here we come 🙂

CHANGELOG.md Outdated
Comment on lines 19 to 20
<!-- * Either mention core version or upgrade -->
<!-- * Using Realm Core vX.Y.Z -->
<!-- * Upgraded Realm Core from vX.Y.Z to vA.B.C -->
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
<!-- * Either mention core version or upgrade -->
<!-- * Using Realm Core vX.Y.Z -->
<!-- * Upgraded Realm Core from vX.Y.Z to vA.B.C -->

Copy link
Contributor

Choose a reason for hiding this comment

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

This one changed because of commander and @commander-js/extra-typings switching versions in bindgen to v11.

Copy link
Member

@kraenhansen kraenhansen Jan 31, 2024

Choose a reason for hiding this comment

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

Yep 👍 It's expected and will also happen when we pull in realm/realm-core#7299.

You could probably leave those updates out of this PR and add them on the PR upgrading to an upcoming Core release instead 👍

Copy link
Member

@kraenhansen kraenhansen left a comment

Choose a reason for hiding this comment

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

If it builds and passes, I'm happy 😊

@kneth kneth force-pushed the kneth/optional branch 2 times, most recently from b01469f to e58efbe Compare February 9, 2024 09:13
@kneth kneth merged commit 02e0f02 into main Feb 9, 2024
7 checks passed
@kneth kneth deleted the kneth/optional branch February 9, 2024 14:59
bimusiek pushed a commit to bimusiek/realm-js that referenced this pull request Mar 14, 2024
…s moving that way (realm#6449)

* Migrating from `tul::Optional` to `std::optional` since Realm Core is
moving that way
* Update core
* Update CHANGELOG.md
* Make linter great again
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants