David Vogt
David Vogt
Analytics now gives you the ability to not only extract slugs from choice questions, but the corresponding labels as well.
This is a first attempt at visualizing a workflow.
# Requirements We need an analytics module that allows us to run queries, get summaries, and find insights into the data stored in Caluma. Requirements are as follows: * Analytics...
During discussion of #1510, a discussion came up regarding our default permissions. Right now, Caluma in it's pristine configuration allows every operation to every user. This is awesome for "playground"...
We should introduce a unified document model, pulling together the "structure" and the "form jexl" perspectives. Currently, they depend on each other, but don't share enough data to be useful....
Caluma uses django-environ with a `.env` file in the project root. When using Caluma as an app, it will most likely be installed as a package. Then, the settings will...
During implementation of #935, the question came up on how we should deal with row documents when removing them from a table. Currently, we detach the row documents by removing...
Analytics fields should be sortable. Analog to form questions, a `ReorderAnalyticsFields` mutation should be implemented. On DB level, the fields should receive a `sort` attribute that's updated according to the...
During manual testing for https://github.com/projectcaluma/caluma/pull/1425, I discovered an issue where ember-caluma would end up in an infinite loop with the following GraphQL query: ```graphql query getFileAnswerInfo($id: ID!) { node(id: $id)...
Since updating to `graphene-django` v3.0.0, I'm getting a `TypeError`, originating from [graphene_django.filter.utils.get_filtering_args_from_filterset()](https://github.com/graphql-python/graphene-django/blob/main/graphene_django/filter/utils.py#L34) (`registry = type._meta.registry`): > TypeError: Form fields cannot be resolved. 'InterfaceOptions' object has no attribute 'registry' The thing...