asciidisco / asciidisco/plugin.video.netflix
Mapping Export To Library to a KeyMap
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
*I'm submitting a ...*
- [ ] bug report
- [x] feature request
- [ ] support request
## General infomration
### Prerequisites
* [x] Are you running the latest version?
### Description
I am trying to map "export to library" from the context menu to a key on my remote. The problem is that the plugin requires two variables ('plugin://plugin.video.netflix/','-1','?action=export&id=[id]&title=[title]','resume:false')
The [id] and [title] to be passed to the plugin to execute the export to library option. However in KeyMaps, it is impossible to know beforehand both variables.
Is it possible to get the plugin to generate both variables in the code, so that all is needed from the KeyMap is to call action=export ?
### Steps to Reproduce
1. Open Netflix plugin
2. Browse to a category
3. Choose a movie/show
4. Invoke the Context Menu
5. Choose "Export to Library"
**Expected behavior:** Clicking on the remote key would automatically add the show to the library
**Actual behavior:** One has to show the context menu and then select the export to library option.
## Context (Environment)
All Environments
### Installation
* [x] I installed the plugin via zip from the Releases page
* [ ] I´m using the Netflix Repo
* [ ] I´m using a different source (Please tell which)
### Operating System
* [ ] Linux (x86/x64)
* [ ] OSX (x86/x64)
* [x] Windows (x86/x64)
* [ ] Linux (ARM)
* [ ] Android
#### Additional informatin on the environment
Windows 10
Contributor guide
Research direction
Start by tracing the existing context-menu “Export to Library” action described in the reproduction steps and how it receives the plugin:// URL, -1, action=export, id, title, and resume arguments. Confirm how a KeyMap invokes plugin actions; done means a remote key can export the currently selected movie or show without opening the context menu.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100