Skip to content

Make UniFFI-exposted APIs public - #7686

Open
bendk wants to merge 1 commit into
mozilla:mainfrom
bendk:bdk/push-pnnuwlrnluoq
Open

bendk wants to merge 1 commit into
mozilla:mainfrom
bendk:bdk/push-pnnuwlrnluoq

Conversation

@bendk

@bendk bendk commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Make all items exposed by UniFFI pub. In practice this probably makes no difference, because these crates aren't consumed by other Rust crates. If they do get added as dependencies, this feels more correct to me. If we're exposing them to the foreign side, we should also expose them to Rust.

Pull Request checklist

  • Breaking changes: This PR follows our breaking change policy
    • This PR follows the breaking change policy:
      • This PR has no breaking API changes, or
      • There are corresponding PRs for our consumer applications that resolve the breaking changes and have been approved
  • Quality: This PR builds and tests run cleanly
    • Note:
      • For changes that need extra cross-platform testing, consider adding [ci full] to the PR title.
      • If this pull request includes a breaking change, consider cutting a new release after merging.
  • Tests: This PR includes thorough tests or an explanation of why it does not
  • Changelog: This PR includes a changelog entry in CHANGELOG.md or an explanation of why it does not need one
    • Any breaking changes to Swift or Kotlin binding APIs are noted explicitly
  • Dependencies: This PR follows our dependency management guidelines
    • Any new dependencies are accompanied by a summary of the due diligence applied in selecting them.

@bendk
bendk requested review from a team, freshstrangemusic, justindarc, mhammond and ncloudioj and removed request for a team October 23, 2026 20:44
@bendk

bendk commented Oct 23, 2026

Copy link
Copy Markdown
Contributor Author

I added a reviewer for each team this affects. I'm guessing this is not too controversial, tell me if you have any concerns. If I don't hear back by the middle of next week, I'll probably assume that you don't mind one way or the other and go ahead and merge it.

pub use crate::stateful::matcher::AppContext;
pub use crate::stateful::nimbus_client::*;
pub use crate::stateful::targeting::*;
pub use crate::stateful::firefox_labs::*;

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Maybe I could have been more selective with the imports here, tell me if you'd prefer that I only import specific items.

@bendk
bendk force-pushed the bdk/push-pnnuwlrnluoq branch from 0821b9c to bfc31d2 Compare October 23, 2026 20:52
@bendk
bendk requested a review from a team as a code owner October 23, 2026 20:52
Make all items exposed by UniFFI `pub`. In practice this probably makes
no difference, because these crates aren't consumed by other Rust
crates.  If they do get added as dependencies, this feels more correct
to me. If we're exposing them to the foreign side, we should also expose
them to Rust.
@bendk
bendk force-pushed the bdk/push-pnnuwlrnluoq branch from bfc31d2 to a17ad26 Compare October 26, 2026 13:39

@ncloudioj ncloudioj left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM, r=nanj.

This branch has not been deployed

No deployments
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