[Dev Tools Feature Request] Temporary Logging for End Users
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.8k
- Forks
- 6.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 442
Description
In order to better support our extensions that are deployed in the store, it would be really nice to have to have an easy way to tell an end user, "Hey, could you enable logging for my extension, then replicate the issue, and send me your logs?" This would accomplish multiple things:
- Users concerned with data privacy could inspect the logs before sending them
- The logs would be limited in scope, instead of ever-growing should this feature be enabled always
- And it could help extension developers better support their published extensions
Raycast version: 1.26.3
Describe the feature and the current behavior/state.
Currently all logs are always disabled for store-deployed extensions
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
The issue names no files, tests, or entry points. Start by locating how logging is controlled for store-deployed extensions and document the required user flow for temporary enablement, inspection, and sharing. Done should include an agreed scope and verification that logging remains disabled outside the temporary session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100