-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Multiline selections only add "quote" markdown to the first line #95
Comments
That is something that needs to be fixed, thanks for pointing it out! Regarding newlines, you can use this plugin: remark-breaks. Just wrap it in a custom extension: const newlines: Plugin = {
transformers: [{
execution: 'sync',
type: 'remark',
transform({ processor }) {
processor.use(remarkBreaks);
}
}]
};
const carta = new Carta({
// ...
extensions: [newlines]
}); Haven't tested but it should work :) |
…refix Addresses bug BearToCode#95 - the `toggleLinePrefix` function was only prefixing the first line of a multline selection and instead of toggling prefixes on and off it would continue adding further prefixes. This change attempts to address both. fix BearToCode#95
The PR includes a bonus fix because it would also add the prefix again instead of removing it when the button was pressed again. It looks like everyone involved (including me, until I figured out what was going on) was assuming that JavaScript's |
🎉 This issue has been resolved in version carta-md-v4.3.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
If I have a larger block of markdown and I want to quote a section of it, it feels intuitive that I should be able to select the block and hit the "quote" button to get it quoted, like this:
But instead I only get the first line marked up:
The "quote" button here on Github behaves in the way that I would expect:
Also Github's quotes treat newlines as newlines instead of insisting on a line break between each line of markdown, which is easier to work with if one is loading text in from somewhere else. That's not really part of this issue, though, just something I notice in using it.
The text was updated successfully, but these errors were encountered: