Comments (6)
it would be very useful to also have two new boolean keys representing the node type:
"is_block_type"
"is_inline_type"
Ok. I just wonder why there should be two more fields. Wouldn't it be enough to just have is_inline_type
. Because in moustache you have 'Inverted Sections' that "will be rendered if the key doesn't exist, is false, or is an empty list".
Is there another reason why there should be two new fields?
having these redundant keys is not DRY, but hopefully it won't hurt either
Having type
and is_inline_type
is no problem in this context, because the JSON is machine-generated and, as you said already, consumed by machines too.
from pml-companion.
Ok. I just wonder why there should be two more fields. Wouldn't it be enough to just have is_inline_type. Because in moustache you have 'Inverted Sections' that "will be rendered if the key doesn't exist, is false, or is an empty list".
You're absolutely right.
Is there another reason why there should be two new fields?
I was just just thinking in terms of consistent naming conventions in view of future similar keys matching to more than two values, in which case it would require providing three boolean keys. That's all. But yes, having a single boolean key is fine.
[ch
Predefined Attribute
I have one question....
Now that we have the autogenerated markdown doc tags-info.md
showing the node/tag properties, it's easier to track all the info from the JSON file.
I've noticed in the Default Attributes section the following:
[ch
→title
→]
[image
→source
→]
It appears that in the generated pml_tags.json
the [ch
node mentions having a "default_attribute_id":"title"
:
"id":"ch",
"type":"block",
"title":"Chapter",
"description":"A chapter or sub-chapter of the document." … etc. …
"attributes":[
{
… etc. …
}
],
"default_attribute_id":"title", <-- here!
I'm not quite sure how to interpret this. Wasn't the title
attribute replaced with the [title
node? What does this key/value pair represent exactly?
from pml-companion.
yes, having a single boolean key is fine.
Ok. The field is_inline_type
has been added. Will be included in PML 2.3. New file: pml_tags.zip
Wasn't the title attribute replaced with the [title node?
You're absolutely right. I just forgot to remove it from default_attribute_id
. It's now fixed, and already corrected in the above file pml_tags.json
.
from pml-companion.
Ok. The field is_inline_type has been added. Will be included in PML 2.3.
Great! Thanks.
You're absolutely right. I just forgot to remove it from
default_attribute_id
Isn't the process entirely automated via introspection?
from pml-companion.
Isn't the process entirely automated via introspection?
It is (to create the JSON file). The problem was in the formal definition of node ch
(line 26 in PML_chapter_formal_node). I had to change that line to default_attribute_id = null
.
from pml-companion.
Fixed in PML 2.3.0.
from pml-companion.
Related Issues (20)
- JavaScript Date function fails in user-defined node HOT 2
- Links URL and Relative Paths HOT 7
- Discrete Headings to Exclude Sections from TOC HOT 5
- Broken Tables in PML 2.3.0 HOT 3
- Problems with [text Node HOT 2
- PMLC: Add Opts to Launch Manuals HOT 3
- Node Repetition via Asterisk HOT 2
- PML Docs: Add Version Info to Ref Man & Create Docs Archive HOT 5
- Why Multiple Heading IDs? HOT 4
- Fatal Conversion Error: [text Inside [title HOT 2
- Resources directory written to '?/.config' when inside Docker container HOT 2
- Resources directory written for non-action commands like help HOT 2
- PMLC v3.1.0 Segfault on Linux HOT 5
- HTML Attributes Ignored on Images HOT 4
- List Enhancements HOT 7
- CSS Option Treats Everything As CSS HOT 8
- Stylesheets Copy-&-Subfolder Prevents CSS Debugging HOT 12
- Parser Inconsistency with Quoted IDs HOT 3
- PMLC 3.1.0 Crashes on Empty [options Node HOT 2
- Delimited Text Syntax and Unbalanced Delimiters HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pml-companion.