Feature Request :: Save/Load profiles

Open
#21 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
frontend, tooling

Research direction

The issue does not name files or tests. Start by locating the devtools front-end option and reproducing the no-op, then compare profile save/load behavior in node-inspector or Chrome DevTools. Done means profiles can be saved and loaded through the option.

Written by the indexing model from the issue text.

Description

Would be handy if we could save and load profiles. This doesn't seem to be working at the moment - nothing happens when I click the option.

Is this something that could be copied from another project, perhaps node-inspector, or chrome's implementation of the dev-tools?

Dominant language
JavaScript
Stars
1.1k
Forks
77
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from c4milo/node-webkit-agent

All issues in c4milo/node-webkit-agent

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.