Ignore non property structures to allow more advanced string building
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No files or tests are named in the issue. Start by tracing how the shown configuration is parsed and how entries without a "$" are handled; determine how non-property parameters should be represented and verify that missing P19 or P21 still produces the requested surrounding text.
Written by the indexing model from the issue text.
Description
I would like to create a structure with name (P9) and birth (P19) and death dates (P21):
P9 (P19 - P21)
But if there is no P19 I want
P9 ( - P21)
and if there is no P21 I want
P9 (P19 - )
Currently I cannot configure this. It would be helpful to allow for 'non property paramaters' in the config.
"*": {
"P9": "$",
"P9.P11": " $",
"P9.P12": ", $",
"P19": " ($",
"P21": " - $)"
}
Ideally I would want to do something like:
"*": {
"P9": "$",
"P9.P11": " $",
"P9.P12": ", $",
"_1": " (",
"P19": "$",
"_2": " - ",
"P21": "$",
"_3": ")"
}
I tried using other Properties, but it appears that when no $ is found, not string is placed. I.e. this hack does not work:
"*": {
"P9": "$",
"P9.P11": " $",
"P9.P12": ", $",
"P23": " (",
"P19": "$",
"P36": " - ",
"P21": "$",
"P71": ")"
}
Where P23, P36, and P71 are required fields in the item, so we expect them to be there. But without a $ the line is ignored.
- Dominant language
- PHP
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ProfessionalWiki/AutomatedValues
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
ProfessionalWiki/AutomatedValues#23 · 10 comments ·
-
enhancement good first issue
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
ProfessionalWiki/AutomatedValues#14 · 1 reaction ·
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 38/100
All issues in ProfessionalWiki/AutomatedValues
Similar issues
-
[Sync EN] Fix session read handler docs: false reports a failure, not a missing session (#5902)Opensync-en
Difficulty 2/5 1-2 days Newbie friendliness 84/100
Maintainers usually reply within 2 days
-
feature-request needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws/aws-sdk-php#3365 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
-
bug status: unverified
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
woocommerce/google-listings-and-ads#3884 ·
Maintainers usually reply within 1 day