nextcloud-libraries / nextcloud-libraries/nextcloud-vue
Concept for different return types of the link picker
Nobody has claimed this yet.
- Dominant language
- Vue
- Stars
- 246
- Forks
- 99
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 103
Description
The link picker would also be useful for other results than links, e.g. text snippets or images. It would be nice if we could have:
- A way to specifify which result types an app wants to receive when launching the picker
- Standardise different result types
- Link (current way of doing it)
- Text (plain text, also works currently but could be more specific)
- Image (as base64 encoded)
We'd need some discussion around wording and naming of this as currently we use the "Add link" / "Pick link" terms but we can probably just adapt that to "Insert link/text/image". For apps that support multiple (like text) we should though have a combining term.
cc @julien-nc as we talked about this idea
cc @jancborchardt @nimishavijay for a first design input on this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation files, tests, or entry points are identified. Start by resolving the proposed result types, payload formats, picker input, and terminology with the linked design participants. Done would be an agreed specification for supported results and the API changes needed to deliver them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100