use some already present dataset (maybe linkedin skills api) to suggest users skillset , just like we are doing with locations for gmaps api , we might not want to hardcode that in our schema
👟 Reproduction steps
No response
👍 Expected behavior
it should suggest all the fields that match with what the user is typing in the combobox
📃 Provide any additional context for the Bug.
we might not want to hardcode all the skills in our schema
👀 Have you spent some time to check if this bug has been raised before?
📜 Description
use some already present dataset (maybe linkedin skills api) to suggest users skillset , just like we are doing with locations for gmaps api , we might not want to hardcode that in our schema
👟 Reproduction steps
No response
👍 Expected behavior
it should suggest all the fields that match with what the user is typing in the combobox
📃 Provide any additional context for the Bug.
we might not want to hardcode all the skills in our schema
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?