-
-
Notifications
You must be signed in to change notification settings - Fork 62.8k
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
format: syntax of in-process
anotation should be *(:construction: in process)*
#7036
format: syntax of in-process
anotation should be *(:construction: in process)*
#7036
Conversation
from (:construction: *in process*) to *(:construction: in process)*
- Applied note `*(:construction: in process)*` translating `in process` to underlying language there where we have previous translated text - Used regex to detect most of notes: `((\*[^\*]+\*)|(_[^_]+_))`
This comment was marked as outdated.
This comment was marked as outdated.
Solve conflicts with branch 'upstream/main' until this PR/commit adding theirs resources too behind conflictive hunk Format incomming resources with new notation too
…nce/homogenize-in-process-notes
in-process
anotation should be `*(:construction: in process)*
in-process
anotation should be *(:construction: in process)*
I see, so this is meant to align |
Yes, sir. Although I also see some of LeanPub notes wrapping all in kursive and others only some parts. Sure there are more data gardening to do 😟 to our oldies eyes. Since access notes have cardinality of 0-1 and notes 0-n, I propose merge all in the same collection to simplify logic. It's posible? It's great? I don't know, too much newbie to understand the scope. If someone ask me for the full normalized format I response with:
where AST tokens are:
How to play with the parser pointing to my forked repo instead of against the upstream? |
I will work on this, but probably not till next week |
There are new addings in Remember replace them with the new format if both PRs are accepted |
Conflicts are with #7065 with moves Vim section to Remember in that file apply new formatting on resolve conficts |
…nce/homogenize-in-process-notes
…ize-in-process-notes
Oh no 😟! Conflicts have been found. Please 🙏, take a moment and address the merge conflicts of your pull request before we can evaluate it again. Thanks in advance for your effort and patience ❤️! |
Oh no 😟! Conflicts have been found. Please 🙏, take a moment and address the merge conflicts of your pull request before we can evaluate it again. Thanks in advance for your effort and patience ❤️! |
Linter failed, fix the error(s):
|
Linter failed, fix the error(s):
|
Co-authored-by: Leithen <lcrider@cvent.com>
What does this PR do?
Improve repo
For resources
Description
The most common syntax seen for each resource annotations across files are
*(bla bla bla)*
where the kursive format wraps parenthesisRegex:
((\*[^\*]+\*)|(_[^_]+_))
So:
(:construction: *in process*)
to*(:construction: in process)*
*-id.md
).Checklist:
Follow-up