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

Update Rust crate floating-ui-leptos to 0.2.0 #391

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 23, 2024

This PR contains the following updates:

Package Type Update Change
floating-ui-leptos (source) dependencies minor 0.1.2 -> 0.2.0

Release Notes

RustForWeb/floating-ui (floating-ui-leptos)

v0.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: RustForWeb/floating-ui@v0.1.3...v0.2.0

Upgrade to Leptos v0.7

Node References

Install leptos-node-ref and replace the node references with AnyNodeRef:

- let reference_ref = NodeRef<Div>::new();
- let floating_ref = NodeRef<Div>::new();
- let arrow_ref = NodeRef<Div>::new();
+ use leptos_node_ref::AnyNodeRef;
+ 
+ let reference_ref = AnyNodeRef::new();
+ let floating_ref = AnyNodeRef::new();
+ let arrow_ref = AnyNodeRef::new();
Reference

Remove .into_reference() from use_floating calls:

  use_floating(
-     reference_ref.into_reference(),
+     reference_ref,
      floating_ref,
      UseFloatingOptions::default(),
  )
Middleware

Install send_wrapper and wrap the middleware vector in SendWrapper:

+ use send_wrapper::SendWrapper;

  let middleware: MiddlewareVec = vec![/* ... */];
  
  use_floating(
      reference_ref,
      floating_ref,
      UseFloatingOptions::default()
-          .middleware(middleware.into()),
+          .middleware(SendWrapper::new(middleware).into()),
  )

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/floating-ui-leptos-0.x branch 3 times, most recently from c9553c7 to 44a7080 Compare December 30, 2024 09:39
Copy link
Contributor Author

renovate bot commented Jan 3, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path packages/primitives/leptos/popper/Cargo.toml --workspace
error: current package believes it's in a workspace when it's not:
current:   /tmp/renovate/repos/github/RustForWeb/radix/packages/primitives/leptos/popper/Cargo.toml
workspace: /tmp/renovate/repos/github/RustForWeb/radix/Cargo.toml

this may be fixable by adding `packages/primitives/leptos/popper` to the `workspace.members` array of the manifest located at: /tmp/renovate/repos/github/RustForWeb/radix/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.

@renovate renovate bot force-pushed the renovate/floating-ui-leptos-0.x branch from 44a7080 to 6174b69 Compare January 3, 2025 15:54
@renovate renovate bot force-pushed the renovate/floating-ui-leptos-0.x branch from 6174b69 to 09e7777 Compare January 8, 2025 13:27
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.

0 participants