Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Pedro Coelho
Beigetreten 13. Mai 2021
·
Letzte Aktivität 16. Okt. 2021
Folge ich
0
Follower
0
Gesamtaktivitäten
3
Stimme
1
Abonnement
1
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Pedro Coelho
Pedro Coelho hat einen Kommentar hinterlassen
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).
Kommentar anzeigen · Gepostet 01. Feb. 2021 · Pedro Coelho
0
Follower
1
Stimme
0
Kommentare