Add referenced node to exported discourse context #246
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dvargas92495
approved these changes
Apr 6, 2024
src/utils/formatUtils.ts
Outdated
| // Remove leading and trailing slashes and start/end modifiers | ||
| const patternStr = titleCondition.target.slice(1, -1).replace(/^\^|\$$/g, ""); | ||
|
|
||
| // Since we aummar there's always a (.*?), we replace it with a specific pattern to capture text within [[ ]] |
There was a problem hiding this comment.
I don't always aummar, but when I do, I prefer to leave it in a comment. 😅
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From a client request to add referenced nodes to exports.
EG: Format = [[EVD]] - {content} - {Source}
then add "Source: [[The source page title]]" to the appended Discourse Context on export
Another workaround for
formatoverspecification, re: #189 😞