You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For an update on this topic, please read this comment.
Background
Angular has evolved significantly with the removal of the legacy view engine in favor of Ivy, and the ecosystem is continuously advancing, as seen with the recent release of Angular v17. This has brought up questions about Algolia’s future support of angular-instantsearch.
Update
We are aware of the challenges and the importance of this library to your projects and are currently evaluating the best path forward, considering the complexities involved with updating the library to be fully compatible with the latest Angular version.
We want to ensure that we approach this transition thoughtfully and effectively and we invite you to share your thoughts on the library's importance to your work and any specific challenges you're facing due to the current compatibility issues.
Feedback
If you have suggestions or are willing to contribute to the library's development, we're open to reviewing pull requests.
Please use this issue to share your feedback, ideas, and any contributions you might have. Your input is crucial as we navigate the future of Angular InstantSearch.
Important
For an update on this topic, please read this comment.
Background
Angular has evolved significantly with the removal of the legacy view engine in favor of Ivy, and the ecosystem is continuously advancing, as seen with the recent release of Angular v17. This has brought up questions about Algolia’s future support of angular-instantsearch.
Update
We are aware of the challenges and the importance of this library to your projects and are currently evaluating the best path forward, considering the complexities involved with updating the library to be fully compatible with the latest Angular version.
We want to ensure that we approach this transition thoughtfully and effectively and we invite you to share your thoughts on the library's importance to your work and any specific challenges you're facing due to the current compatibility issues.
Feedback
If you have suggestions or are willing to contribute to the library's development, we're open to reviewing pull requests.
Please use this issue to share your feedback, ideas, and any contributions you might have. Your input is crucial as we navigate the future of Angular InstantSearch.