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 host binding migration #528

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

Conversation

ostromeckyp
Copy link
Contributor

No description provided.

@ostromeckyp ostromeckyp force-pushed the feat/migrate-host-binding-to-host-in-decorator branch from be0b123 to 24f0916 Compare December 3, 2024 10:03
@ostromeckyp
Copy link
Contributor Author

@eneajaho kindly asking for a review

Comment on lines +1 to +7
---
title: Queries Migration
description: Schematics for migrating from decorator-based Queries to Signal-based Queries
entryPoint: plugin/src/generators/convert-queries
badge: stable
contributors: ['enea-jahollari']
---
Copy link
Collaborator

Choose a reason for hiding this comment

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

This needs to be updated

contributors: ['enea-jahollari']
---

Recent releases of Angular have deprecated the `@HostBinding` and `@HostListener` decorators, replacing them with `host` defined properties. This migration schematic will help you convert your existing `@HostBinding` and `@HostListener` decorators to the new `host` properties.
Copy link
Collaborator

Choose a reason for hiding this comment

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

The decorators are not yet deprecated

import { convertHostBindingGenerator } from './generator';
import { ConvertHostBindingGeneratorSchema } from './schema';

const filesMap = {
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'd like to see some more test cases. And before we merge this one, we will need to make sure that we don't break apps.

@eneajaho
Copy link
Collaborator

eneajaho commented Jan 2, 2025

@ostromeckyp This PR needs a rebase.

Also, just to let you know, we probably will get this merged in ngxtension, but I'm also working on a prototype that does the same thing, but working on getting it directly in the Angular repo, as that would make it easier for everyone to use.

But, because ngxtension already supports a lot of schematics, we can get this merged and out before I can get mine ready for the Angular one.

Thanks for creating this!

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