ProfessionalWiki / ProfessionalWiki/ModernTimeline

Possibility to pass parameters with multiple values to the template

Open
#21 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
19
Forks
11
PR merge metrics
No merged PRs in 30d

Description

With the format "moderntimeline", it’s currently not possible to pass parameters (properties) with multiple values to the template for the slide area. When the query results in multiple values for a print-property, only the first value will be passed through to the template; the other values will be ignored and are thus not available within the template domain.

I've found a "workaround" for this issue (simply querying for the desired values), but that would technically be very inefficient for timelines with many events/dates. Every event will then result in one or more queries for displaying information...

The desired solution would be - imho - that all values will be passed through the template, f.e. separated by semicolons. The #arraymap parser function can then be used for further handling of the data for display.

Example of current situation (still under development, so might change): TheaterEncyclopedie

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the moderntimeline result-format entry point and trace how print-properties are collected before the slide template receives them. Reproduce the multi-value case from the TheaterEncyclopedie example; done means every returned value is available in the template with a delimiter suitable for #arraymap, without extra per-event queries.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.