Skip to content
This repository was archived by the owner on Nov 28, 2022. It is now read-only.

feat: splitting out our current markdown engine to a new package#514

Merged
erunion merged 1 commit intomasterfrom
feat/split-out-legacy-markdown-engine
Mar 10, 2020
Merged

feat: splitting out our current markdown engine to a new package#514
erunion merged 1 commit intomasterfrom
feat/split-out-legacy-markdown-engine

Conversation

@erunion
Copy link
Member

@erunion erunion commented Mar 10, 2020

With #436 coming up very soon, I'm working on a deployment strategy and given that our new Markdown engine is currently being enabled in production via a flag, and is unfortunately reserving the v5 release tag (#458), we're making the decision to split out our existing (legacy) Markdown engine to a new package: @readme/markdown-magic.

With a separate package, we can then merge the new Markdown processor into master and flip between the different parsers based on what we want to use for the project at hand.

Once this is merged in, I'll package it up into NPM and branch off #458 again with some work to allow us to toggle between the different engines.

@erunion erunion added the scope:dependency Pull requests that update a dependency file label Mar 10, 2020
@erunion erunion requested a review from rafegoldberg March 10, 2020 00:55
@erunion erunion merged commit 087374d into master Mar 10, 2020
@erunion erunion deleted the feat/split-out-legacy-markdown-engine branch March 10, 2020 01:03
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

scope:dependency Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant