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

Angular wrapper (new) #628

Conversation

donaldxdonald
Copy link
Contributor

Hi @davidjerleke ,

Long time no talk! I apologize for the delay, as I've been quite busy lately. I wanted to let you know that I've finished all the Angular wrapper code and documentation. It's all ready for review. The context is here #18 .

  • embla-carousel-angular
  • embla-carousel-playground-angular
  • docs/get-started/angular

There are a few points that need to be clarified:

Bundling

All library wrapper packages have the same rollup.js structure which bundles the code.

Angular has its own webpack-based Angular CLI for bundling, and since the Angular ecosystem is almost exclusively packaged using the Angular CLI, it makes more sense to use it for bundling.

Publishing

As mentioned above, embla-carousel-angular is packaged using the Angular CLI, which outputs the build to the dist folder (or some other non-root path).

All other libraries in the embla-carousel repository are packaged with rollup and exported directly to the root directory of the library, and then the npm publish command is executed in CI/CD, which is not directly usable in embla-carousel-angular.

So I've changed the release command in cd.yml to run yarn release so that I can use a specific release strategy for each library.

Thank you for your patience, and once again, I apologize for the delay. I appreciate your continued support and guidance throughout this process.

@davidjerleke
Copy link
Owner

Hi @donaldxdonald,

Thank you for your efforts. This is great! And no worries. As I mentioned there’s no deadline involved. I’m just happy that you want to contribute 🙂.

I will review this PR as soon as possible. I just want to mention that I have two things I’ve started that I want to finish before jumping into this. Thank you for your patience!

Best,
David

@davidjerleke davidjerleke linked an issue Nov 11, 2023 that may be closed by this pull request
@davidjerleke davidjerleke added feature request New feature or request angular Issue is related to Angular labels Nov 12, 2023
@davidjerleke
Copy link
Owner

Hi @donaldxdonald,

I'm done with the two other things now. If you rebase your branch/changes on my master branch I will review this PR afterwards.

Thanks!
David

@donaldxdonald
Copy link
Contributor Author

Done. @davidjerleke

@davidjerleke davidjerleke self-assigned this Nov 16, 2023
@davidjerleke
Copy link
Owner

Hi @donaldxdonald!

Hope you're doing great. I caught Covid so been off for some time but I'm back now and I just started looking into this PR. Please refrain from pushing new stuff until I'm done. Thanks for understanding 🙂.

Best,
David

@davidjerleke davidjerleke removed feature request New feature or request angular Issue is related to Angular labels Dec 4, 2023
@davidjerleke
Copy link
Owner

@donaldxdonald closing this because I've updated the original (first) Angular PR and fixed the git history there. Don't worry, all changes in this branch are there now:

@davidjerleke davidjerleke removed their assignment Dec 4, 2023
@donaldxdonald donaldxdonald mentioned this pull request Jan 3, 2024
3 tasks
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.

None yet

2 participants