source namespace: support different source (raw) formats

Open
#8 2 comments 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
api

Research direction

Start by reviewing the source namespace description at http://source.scripting.com/ and compare the current source:markdown behavior with the proposed source:raw format attribute. Resolve whether format values should be simple names or MIME types, then define the supported formats and acceptance criteria before implementation.

Written by the indexing model from the issue text.

Description

Hello,

I was reading the http://source.scripting.com/ and my understanding is that presently this namespace cannot be used for non-Markdown sources (e.g. ReStructured Text, AsciiDoc or other). A possible alternative would be to have instead of source:markdown a source:raw (or some other name) element with a required attribute (format or possibly type) to denote the format. I'm thinking the attribute values could be either a simple string (markdown, asciidocto, rst) or possibly even the registered MIME type (if any) of the raw content.

Dominant language
JavaScript
Stars
104
Forks
3
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 scripting/reallysimple

All issues in scripting/reallysimple

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.