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(angular): remove unnecessarily generated code for remotes #9844

Merged
merged 1 commit into from Apr 19, 2022

Conversation

Coly010
Copy link
Contributor

@Coly010 Coly010 commented Apr 14, 2022

We shouldn't generate unnecessary code when generating remote apps

@Coly010 Coly010 self-assigned this Apr 14, 2022
@nx-cloud
Copy link

nx-cloud bot commented Apr 14, 2022

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 616155c. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch


✅ Successfully ran 14 targets

Sent with 💌 from NxCloud.

@vercel
Copy link

vercel bot commented Apr 14, 2022

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nrwl/nx-dev/4WKHdJBSwSsJABuhHSU2rLtqpHeR
✅ Preview: Ignored

@Coly010 Coly010 requested review from jaysoo and removed request for jaysoo April 14, 2022 19:24
Copy link
Member

@leosvelperez leosvelperez left a comment

Choose a reason for hiding this comment

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

LGTM! 🎉

Left a non-blocking comment to consider.

Comment on lines +69 to +73
const component =
tree.read(pathToComponent, 'utf-8').split('templateUrl')[0] +
`template: '<router-outlet></router-outlet>'
})
export class AppComponent {}`;
Copy link
Member

Choose a reason for hiding this comment

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

imho, it would be better if we have the full template for the component here rather than splitting by a property based on what was previously generated. It's a small component, so the template would be small. It should be clearer, and we'd also reduce the potential maintenance associated with relying on a previous generation that could change and that we don't need to rely on. Regardless of a previous generation, we know the content of what we want in this component.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Very good point. I will add this as an additional cleanup PR

@Coly010 Coly010 merged commit fc235de into nrwl:master Apr 19, 2022
@Coly010 Coly010 deleted the angular/remove-dead-code-gen branch April 19, 2022 09:36
@github-actions
Copy link

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants