Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output structure? #4

Open
jlord opened this issue May 30, 2014 · 2 comments
Open

Output structure? #4

jlord opened this issue May 30, 2014 · 2 comments

Comments

@jlord
Copy link
Owner

jlord commented May 30, 2014

Right now when you run this, in whatever directory you're in you'll get:

  • comments.json
  • md/
    • an-issue.md
  • html/
    • an-issue.hml

This is not the best. It should perhaps give you one folder, with each of these things in it? Or not give you comments.json at all probably?

cc @muan

@jbenet
Copy link

jbenet commented Jun 1, 2014

What about this?

  • issues/ (can be remapped to .gh-issues or something)
    • <issue number>/
      • issue.json - put the metadata here (labels, assignee, etc.)
      • <comment number>-<author>.md <-- this
      • <comment iso date>-<author>.md <-- or this
      • issue.html - all comments rendered together (should be renderable later?)

(separates comment srcs into their own file.)

@jlord jlord mentioned this issue Jun 15, 2014
10 tasks
@tiger12506
Copy link

I think the directory structure should match that of github's.

For example, see the url for this issue:
https://github.com/jlord/offline-issues/issues/4

That way a Save As from the online browser could easily be searched and replaced for all links and the site url change to file:// references, like so:
file://<path-to-offline-dir>/jlord/offline-issues/issues/4

@krlmlr krlmlr mentioned this issue Apr 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants