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

feat: add @ngneat/helipopper/config #166

Merged
merged 1 commit into from
Nov 20, 2024

Conversation

arturovt
Copy link
Contributor

@arturovt arturovt commented Nov 19, 2024

In this commit, we add a new subpackage called @ngneat/helipopper/config.
This change is intended to separate configuration logic from UI-related functionality.
The configuration should be imported at the root level, while the UI components should
only be imported when necessary. Previously, importing the library at the root
level (when providing the configuration) caused the bundler to include everything in the
main bundle immediately.

With this approach, the configuration is bundled separately at the root level and
includes only the provider functions.

Additionally, while we had already added a loader function, to avoid breaking the
provideTippyConfig signature, we introduced a separate function called provideTippyLoader,
which exclusively accepts a loader function.

The provideTippyConfig has been reverted to return a provider (not an environment provider),
becuase it might be provided at the component level too.

Copy link

stackblitz bot commented Nov 19, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

In this commit, we add a new subpackage called `@ngneat/helipopper/config`.
This change is intended to separate configuration logic from UI-related functionality.
The configuration should be imported at the root level, while the UI components should
only be imported when necessary. Previously, importing the library at the root
level (when providing the configuration) caused the bundler to include everything in the
main bundle immediately.

With this approach, the configuration is bundled separately at the root level and
includes only the provider functions.

Additionally, while we had already added a `loader` function, to avoid breaking the
`provideTippyConfig` signature, we introduced a separate function called `provideTippyLoader`,
which exclusively accepts a loader function.

The `provideTippyConfig` has been reverted to return a provider (not an environment provider),
becuase it might be provided at the component level too.
@arturovt arturovt marked this pull request as ready for review November 19, 2024 10:50
@arturovt
Copy link
Contributor Author

@NetanelBasal could you merge? I'll make a next release.

@NetanelBasal NetanelBasal merged commit 8d713e9 into ngneat:master Nov 20, 2024
2 checks passed
@arturovt arturovt deleted the feat/config-lib branch November 20, 2024 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.

2 participants