packagecontrol / packagecontrol/thecrawl
More README renderers?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 4h 53m
- Merged PRs (30d)
- 14
Description
Currently we only render on the client side, thus only JS-based parsers/renderers. We could fetch any lib that works in the browser on demand.
We also have Cloudflare workers, but they also only speak JS -- which was a bit surprising to me tbh.
Other than that we use the GitHub infrastructure which has runners for every language and OS but it is more challenging to program. But by far more interesting too.
Progress is when people research (in some depth) which browser lib is needed for which markup format, and how to use it (in a safe way).
Another way to think about this, is to have just syntax highlighting for such formats (ideally the same tokenization as in Sublime Text 😁).
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or entry point is named. Research browser-based JavaScript parsers and renderers for the markup formats under consideration, including their safe on-demand use; document which formats each library supports and whether syntax highlighting could share Sublime Text tokenization. Done means a researched comparison that narrows the implementation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100