Hi @vogloblinsky this PR fixes the current issues with input, output and model signals. This is causing issues with the Storybook Controls Addon (see storybookjs/storybook#28412), which gets fixed by this PR.

Hi,
Is it possible to add a unit test for the signal you added in the fixtures ?
Thanks

Hi,
Is it possible to add a unit test for the signal you added in the fixtures ?
Thanks

Yes sure, can you give me a hint where I must add the unit test?

https://github.com/compodoc/compodoc/blob/develop/test/src/cli/cli-generation.spec.ts works with the folder ./test/fixtures/sample-files/where you update one fixture

https://github.com/compodoc/compodoc/blob/develop/test/src/cli/cli-generation.spec.ts works with the folder ./test/fixtures/sample-files/where you update one fixture

Thank you for the hint. I have added tests.

@vogloblinsky is there anything else needed to get this PR merged?

Please someone give some love to this PR before it becomes stale. This is one of the most critical issues with Compodoc now that Angular seems to have embraced signals.

I would also love to see it merged and released soon.

@vogloblinsky Sorry to tag you again, but it would be fantastic if this PR could be merged soon 🙂

Thanks a lot for the PR

Unit tests are wrong, but may be not in sync with last developments, i will fix that asap.

Hey @vogloblinsky what is the current progress of this? When can we expect a new release containing this PR?

@vogloblinsky will this be released to NPM soon? We really need this fix for storybook.

I built it locally and linked it to the project with a storybook and works like a charm.

@kklimczak cool!!

does it work with inputs with variable default value and transform functions?
For example: input.required(DEFAULT_VALUE, {transform: booleanAttribute})

@rojasjandro89 Is it valid? In my case DEFAULT_VALUE is false.

I get a type error:

@kklimczak my bad, we can't specify a initial values in a required input. Can you try removing required?

@rojasjandro89

Is there any info on when we can expect this to be released?

@vogloblinsky

Hi Vincent,
First of all, thanks a lot for your work on this library - it's been super helpful.

I wanted to ask if you have any plans to publish a new release that includes this fix for Angular signals? At the moment, without this fix, Storybook (which depends on your library) can't properly display fields using Angular signals, and it's causing some trouble in my workflow.

Really appreciate your time and effort - let me know if there's anything I can do to help move this forward.

Best regards,
Andrew

@sonallux unit tests are failing in the develop branch and it looks that started with the merger of this PR. I'm guessing that is the reason this hasn't been released to npm yet. Have you looked at this at all?

@sonallux I might have found the issue. You change this function to assign to deps.propertiesClass instead of deps.properties.

src/app/compiler/angular-dependencies.ts

if (IO.properties) {
-  deps.properties = IO.properties;
+  deps.propertiesClass = properties;
}

Unit tests are wrong, but may be not in sync with last developments, i will fix that asap.

@vogloblinsky Now that unit tests are fixed, can we please get a new patch version with this change released to npm?

We need this fix ... badly