• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

scriptype / writ-cms / 14434359401 / 4
38%
master: 38%

Build:
DEFAULT BRANCH: master
Ran 13 Apr 2025 11:26PM UTC
Files 108
Run time 3s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

13 Apr 2025 11:25PM UTC coverage: 75.427%. Remained the same
14434359401.4

push

github

scriptype
[CM2] Introduce deep categorization

This is a combination of 3 commits. Brace yourself.

For now the taxonomy depth is max 3. Because why not.

This required looking up to parent context for content modelling
information, instead of reaching out to the collection. So, throughout
the depth of the taxonomy, content modelling can manipulate the cascade.

To achieve that, the context object is converted into a stack. An
ImmutableStack class is used to pop() it without worrying. It has a
throwUntil() to dig the stack until reaching a point of interest (for
example digging the context to find a collection). That was needed to
avoid passing post and category contexts to tags, as tags don't carry a
hierarchial-relationship in respect to them.

Now, each subCategory can define content-modelling attributes in its
index file. Therefore, each subCategory can have a custom indexFileName
and custom names for its subCategories and posts. For example:

Demos (collection contentType: DemoPortfolio)
  - CSS (category contentType: Technology)
    + CSS-Only (category contentType: Technique)
    + Sliding Doors (category contentType: Technique)
  - Three.js
  - Whatever

The easiest way to deal with rendering subCategories was to merge
the rendering counterpart of models into the models themselves. So,
now, in addition to match() and create(), there's a render(). The render()
is pretty scrappy for now and probably needs more thinking. One of the
main ideas in this implementation is to nest the rendering of the
model's child entities (e.g. for a category, rendering of subCategories,
posts, attachments) into the models' render(). When root render()s,
render flows downstream from there. So, CM2's rendering counterpart is
now only the renderer itself, there's no more views.

Invent something called 'levelPosts' in Category. It contains only the
posts belonging to the category's specific depth. The regular 'posts'
field contains all posts downstream. This was particularly ne... (continued)

482 of 756 branches covered (63.76%)

Branch coverage included in aggregate %.

2259 of 2878 relevant lines covered (78.49%)

36.4 hits per line

Source Files on job 14434359401.4
  • Tree
  • List 108
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 14434359401
  • 3fbc18c8 on github
  • Prev Job for on master (#14434185121.2)
  • Next Job for on master (#14457164071.4)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc