-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
ctx.viewModeTpl is undefined after updating to 1.9 #98
Comments
Hello, the library is now using Standalone API. |
Appreciate the quick response, (and the updated README ;)) Did not realize the Directive imports were mandatory. Added them and it works like expected. Thanks again! |
Hmm, seems it does not completely work as expected still. Yes, the errors are gone, but when I click the text in viewMode it does nothing, and only after I resize the window the viewMode changes to editMode. Want me to open a new issue or? |
Yes please for a better understanding, please provide as much context as possible so I can help. |
@geromegrignon fyi Decided to dive a bit deeper and try some stuff out. Installed a fresh Angular 17 with Ionic and then it worked without issues, so I thought I'd try upgrading my own project to 17 and that seems to have fixed it. So wont be creating a new issue, just thought I'd let you know. Thanks again for the fast replies, really appreciate it. |
I'm submitting a
Bug report
Current behavior
When updating a project, I noticed the error as also mentioned in this issue, so I thought I'd update to the newest version of this package.
However this resulted in a non-functional page, as it now gives the error when going to the page
It compiles without issues, however also my tests now fail with a similar error.
For example the test
results in:
Failed: Cannot read properties of undefined (reading 'tpl')
:Expected behavior
That the package should work like before the update.
Minimal reproduction of the problem with instructions
component.ts :
component.html:
What is the motivation / use case for changing the behavior?
No response
Environment
No response
The text was updated successfully, but these errors were encountered: