OK, so I talked with the team and the field in this beta version of slice-machine-ui only supports 'links to web'. The content relationship supports 'links to documents' and neither supports 'links to media'.
I have requested the team to add support for all 3 of these cases to the link field. Hopefully this will be added in the next BETA release shortly.
I will update you here once this is done.
Thanks.
Any ideas if this is still in the works? I'm still having to go into the models and manually update this to allow both types of links (web and document) which is definitely not ideal
Hi Dan,
With the latest stable version of Slice Machine UI this should work, you'll need to update you Slices and push them to Prismic to get this functionality.
Thanks.
I've been working on 0.1.0 for the last 2 weeks and I'm still not seeing this. This is the latest release as far as I can tell, but if I go up to 0.1.0-beta-9 I still don't see any option to choose what type of link I'm creating.
Even if I create a new link I still don't see this
Am I missing something?
Hi @dan ,
The latest version is stable 0.1.0, so it's out of beta.
Try deleting your node_modules and package-lock.json files, then in your package.json change slice-machine-ui to "slice-machine-ui": "^0.1.0".
Finally, run npm install again and you should have the latest version.
Thanks.
Hi @Phil,
I've deleted my node_modules folder and yarn.lock file but that hasn't changed the slice-machines-ui
It's at ^0.1.0 but what I'm seeing (after deleting everything, running yarn again and restarting the servers) is still the same as above.
Any ideas?
I'm going to test this on my side now to be sure.
Thanks.
I'm seeing this behaviour also, it should have been shipped with this version. I'm following up with the team to get more information.
So in the current version of slice-machine-ui the 3 types of links are 3 different fields:
I'm discussing with the team that the default link field should support all 3 of these use cases. Hopefully we'll get this for the next release. I'll update you here once I have more info.
Great! It really doesn't make sense that it works this way as it's quite restricting (users regularly want to link both internally and externally) and the rich text links already work like this (where you can select any link type).
Thanks for looking into it.
This is being tracked as an open feature request.
If you have another use-case for this feature, you can 'Flag' this topic to reopen. Please use the 
button to show your support for the feature and check out our Feature Request Guidelines.
thank you! that helped my solve this 
"dependencies": {
"@prismicio/client": "^5.1.0",
"@storybook/preset-scss": "^1.0.3",
"next": "12.0.7",
"next-slicezone": "^0.1.3",
"prismic-reactjs": "^1.3.4",
"react": "17.0.2",
"react-dom": "17.0.2",
"sass": "^1.45.1",
"swiper": "6.8.4"
},
"devDependencies": {
"@babel/core": "^7.16.5",
"@storybook/addon-actions": "^6.4.9",
"@storybook/addon-essentials": "^6.4.9",
"@storybook/addon-links": "^6.4.9",
"@storybook/react": "^6.2.8",
"babel-loader": "^8.2.2",
"babel-plugin-react-require": "^3.1.3",
"eslint": "8.5.0",
"eslint-config-next": "12.0.7",
"eslint-plugin-storybook": "^0.5.5",
"slice-machine-ui": "^0.1.2"
}
I'm still seeing this issue
Hello @jibin, for the moment, the functionality is still the same. You need to add a Content Relationship field to select internal documents from your repository.
Hi Everyone,
This is now available from Slice Machine v 0.2.0, you will need to make a change in your Slice and push the updated Custom Type to Prismic.
Thanks.