node-red / node-red/node-red-nodes
custom consumer key/secret in twitter node
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
currently twitter node is using a hard coded consumer key and consumer secret in its node definition,
is it possible to change this node in order to get these parameters from users to allow them use their own generated keys?
maybe its good to use predefined consumer key/secret if user didn't supply its own keys.
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
Start by locating the Twitter node definition and the hard-coded consumer key and secret described in the issue. Determine how node users currently configure credentials; done should allow user-supplied keys while preserving the predefined keys when none are supplied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100