Ricerche recenti
Nessuna ricerca recente

Pedro Coelho
Data ingresso 13 mag 2021
·
Ultima attività 16 ott 2021
Seguiti
0
Follower
0
Attività totali
3
Voto
1
Abbonamento
1
PANORAMICA ATTIVITÀ
BADGE
ARTICOLI
POST
COMMENTI NELLA COMMUNITY
COMMENTI AGLI ARTICOLI
PANORAMICA ATTIVITÀ
Ultima attività di Pedro Coelho
Pedro Coelho ha commentato,
Hi Dave,
I've been struggling with the same problems as Arne: the `created_at_with_time` field's usefulness would be greatly improved if the field had at least second level precision, instead of minute. The `created_at_with_timestamp` placeholder exists for the ticket, so it's just a matter of porting it to the comment model as well. That would definitely solve my problem at least.
Another thing that would be immensely useful would be being able to list the ticket's custom fields without prior knowledge about what fields exist, similar to calling the `/api/v2/tickets` endpoint.
As for the weirdness in the `tickets.comments`: that looks like the standard output from printing a Ruby on Rails model (or using the inspect method). While I certainly can't argue about whether it is intentional or not, it is not usually a good practice, as it may lead to a couple of security problems down the road (without extra configuration, if you add extra fields to the Comment model they will show up in that representation whether you want it or not).
Visualizza commento · Data ultimo post: 01 feb 2021 · Pedro Coelho
0
Follower
1
Voto
0
Commenti