fix: NavContainer not exported

[Zenya4]

Closes #1297

📑 Description

See #1297

Status

• Not Completed
• Completed

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• I have checked the page with https://validator.unl.edu/
• All the tests have passed
• My pull request is based on the latest commit (not the npm version).

Summary by CodeRabbit

• New Features
  • Added navigation container for improved app navigation.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
flowbite-svelte	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 28, 2024 7:50am
flowbite-svelte-update	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 28, 2024 7:50am

[coderabbitai]

Walkthrough

This update marks a pivotal improvement in the project, focusing on enhancing the usability of the NavContainer component by exporting it directly from the main index.js file. This change simplifies the import process for end-users, aligning with the initial design intentions and improving the developer experience.

Changes

File Path	Change Summary
src/lib/index.js	Exported NavContainer from .../NavContainer.svelte

Assessment against linked issues

Objective	Addressed	Explanation
Export NavContainer directly in index.js (#1297)	✅

Possibly related issues

• Error with Svelte 5.0.0 #1185: Although this PR doesn't directly address the specific issues of compatibility and import/export mismatches with Svelte 5.0.0, improving the export structure could indirectly benefit the project's adaptability to such changes.
• JSX element type 'Tabs' does not have any construct or call signatures. flowbite-react#1259: Not directly related, as the changes pertain to a different library (flowbite-svelte vs flowbite-react), but it highlights a common theme of addressing component export issues for better usability and compatibility.

🐇🎉
To the code that binds,
A simpler path we find.
With NavContainer aligned,
A smoother journey, designed.
🚀🌟

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 214f3de and c1d2a97.

Files selected for processing (1)

• src/lib/index.js (1 hunks)

Additional comments (1)

src/lib/index.js (1)

• 119-119: The addition of NavContainer to the exports in index.js correctly addresses the issue documented in NavContainer not exported from index.js #1297, allowing users to import NavContainer directly from the flowbite-svelte package. This change enhances the usability of the component and aligns with the project's structure and conventions.

[jjagielka]

NavContainer is not exported by design. It's an internal class used by Navbar.
See the docs: https://flowbite-svelte.com/docs/components/navbar#Navbar_container
The usage is:

<Navbar let:NavContainer color="primary">
  <NavContainer class="border px-5 py-2 rounded-lg bg-white dark:bg-gray-600">
    ....

[shinokada]

I close the PR for now.
Thank you for your contribution.