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 secondary entrypoint schematic #28723

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

Conversation

Jefiozie
Copy link
Contributor

@Jefiozie Jefiozie commented Oct 28, 2024

PR Checklist

Please check to confirm your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

There is no easy way to generate a secondary entrypoint

Issue Number: #19070

What is the new behavior?

This PR adds the ability to generate a secondary entrypoint in a library project. It cannot be used without a library project.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

I've copied some helper utils from other schematics. I'm happy to make a other PR to add these to the utility parts with proper tests on it. Not updated the docs as this is I think in a other repo?

Pinging @SanderElias he mentioned there was nothing in the cli and encourage me to make this change 👍

@angular-robot angular-robot bot added the detected: feature PR contains a feature commit label Oct 28, 2024
Copy link

@SanderElias SanderElias left a comment

Choose a reason for hiding this comment

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

Looks good to me! Ship It!

@alan-agius4 alan-agius4 added the needs: discussion On the agenda for team meeting to determine next steps label Oct 28, 2024
@alan-agius4 alan-agius4 self-assigned this Oct 28, 2024
@Jefiozie
Copy link
Contributor Author

Hi @alan-agius4 I saw that you added the discussion label. Any pointers what the discussion is about? I'm happy to join the discussion to see what we can improve or my point of view on things.

@alan-agius4
Copy link
Collaborator

alan-agius4 commented Oct 29, 2024

@Jefiozie, since this is adding a new public API, we need to discuss this internally, and make sure that the team is on board with this.

@Jefiozie
Copy link
Contributor Author

@alan-agius4 that does make sense, I will wait then and rebase this PR until you / the team comes back with feedback.

@Jefiozie
Copy link
Contributor Author

Jefiozie commented Nov 4, 2024

@alan-agius4 the PR is up-to-date with latest changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
detected: feature PR contains a feature commit needs: discussion On the agenda for team meeting to determine next steps
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants