Templating for contact protocols about chandler

[Martijn-Bos]

Where would this feature be possible to implement? There is a significant possibility in scope.

[phorcys420]

Where would this feature be possible to implement? There is a significant possibility in scope.

Hello, sorry, I don't understand your question.
Can you maybe elaborate on what you mean ?

[Martijn-Bos]

If I correctly understand there would be a set amount of possible templating tags that are transformable
%contact_id% - id of contact.
%gift_description% - description of a gift.
%address_id% - id of address
%postal_code% - postal code

Wherever a string will be presented in the frontend and within the context of that page it is possible to figure out which contact, gift or address(etc) is actually meant, the tag will be transformed to the actual data.

If you're looking at a contact page of Mahatma Gandhi, which has id 12 in your database it would be able to transform the following link:
https://somesite.com/%contact_id%/profile
Would become
https://somesite.com/12/profile

For a lot of templating there is a specific need for context for the tags that need to be filled. If you're on a contact index page, you can't fill any contact_id since Chandler is not able to know which exact contact is meant.

As the idea is awesome I am wondering where you'd want this to be available and where it would be interesting to implement - every extra added tag and page where tagging is possible would increase the time investment needed.

[phorcys420]

I don't think you understood it like I meant it.

if you go to /settings/personalize/contactInformationType on your chandler instance, you are able to add contact information types. (image)

Like that :

• declaring the protocol
• adding the contact info

And that would format the link to be https://website.com/@/something/profile

In #459 I talked about something like adding in an "ID" field to the existing contact info stuff, that way you could distinguish name and ID.

[Martijn-Bos]

I did indeed misunderstand. Seems like a great implementation.