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
As proposed by Daniel and Pooya, it would be beneficial to include 'Algolia' in the naming of the composables (as they are auto imported) to avoid conflicts.
It was already introduced in version 0.8.3 with a new composable called 'useAlgoliaRecommend'. The next step now is to rename other composables to avoid future conflicts.
In order to avoid unnecessary issues in production for users, I would like to create a two step process of implementing that:
Duplicate current composables but with the names changed to the ones proposed in the previous section and add a console.warn for current composables that they will be deprecated with the next major version in favor of the new named components. Modify the readme warning from the current one that is already outdated to inform the users that there are plans to rename composables to better fit the nuxt 3 auto import approach.
In the next major version remove the old composables and just leave the new ones.
resolvedIndicates that the issue or discussion was resolved
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
As proposed by Daniel and Pooya, it would be beneficial to include 'Algolia' in the naming of the composables (as they are auto imported) to avoid conflicts.
It was already introduced in version 0.8.3 with a new composable called 'useAlgoliaRecommend'. The next step now is to rename other composables to avoid future conflicts.
I propose following names:
useAlgolia
->useAlgoliaRef
useSearch
->useAlgoliaSearch
useSearchForFacetValues
->useAlgoliaFacetedSearch
useInitIndex
->useAlgoliaInitIndex
useAlgoliaRecommend
-> already live.In order to avoid unnecessary issues in production for users, I would like to create a two step process of implementing that:
Beta Was this translation helpful? Give feedback.
All reactions