-
Pull out content from <content> tag in exported XML file
-
Replace blank lines w/ </p><p>, add <p> as first line and </p> as last line
-
Put that content into the body of a basic HTML document structure (so it looks like an HTML file)
-
convert using
pandoc --no-wrap -f html -t asciidoc post-content.html > post-content.adoc
-
use sed to cleanup
sed -i s/^image:/image::/ post-content.adoc
- Write functions() in lower case, KEYWORDS in upper.
STARTeach keyword clause
ONa new line.- Use either
camelCaseorsnake_casefor node identifiers but be consistent. - Relationship type names should use
UPPER_CASE_AND_UNDERSCORES. - Label names should use
CamelCaseWithInitialCaps. MATCH (clauses)-->(should)-->(always)-->(use)-->(parentheses)-->(around)-->(nodes)- Backticks `cân éscape odd-ch@racter$ & keyw0rd$` but should be a code smell.
This file contains hidden or 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
| import java.io.IOException; | |
| import java.net.URLClassLoader; | |
| import java.nio.file.Files; | |
| import java.nio.file.Paths; | |
| import java.nio.file.Path; | |
| /** | |
| * Example demonstrating a ClassLoader leak. | |
| * | |
| * <p>To see it in action, copy this file to a temp directory somewhere, |
This file contains hidden or 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
| /* | |
| { | |
| "talks": [{ | |
| "title": "Building 'Bootiful' Applications", | |
| "abstract": "Alright, so maybe “bootiful” won’t ever work,...", | |
| "topics": ["topic"], | |
| "room": "Auditorium", | |
| "timeslot": "Wed 29th, 11:00-11:50", | |
| "speaker": { | |
| "name": "Josh Long", |
This file contains hidden or 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
| Feature: karate answers 2 | |
| Background: | |
| * url 'http://localhost:8080' | |
| Scenario Outline: given circuit name, validate country | |
| Given path 'api/f1/circuits/<name>.json' | |
| When method get | |
| Then match $.MRData.CircuitTable.Circuits[0].Location.country == '<country>' |
There are 28 static site generators that support AsciiDoc sourcing.
There are 4 possible serialization format when using avro:
- Avro Json encoding
- Avro Data Serialization (https://avro.apache.org/docs/current/spec.html#Data+Serialization) Binary format with an header that contains the full schema, this is the format usually used when writing Avro files
- Avro Single Object Encoding (https://avro.apache.org/docs/current/spec.html#single_object_encoding) Binary format with an header with only the fingerprint/id of the schema, this it the format used by Kafka (see this
- Avro Binary Encoding (https://avro.apache.org/docs/current/spec.html#binary_encoding)