Hélène Martin

Sounds good to me to document the behavior for now and keep an eye on this. The issue you linked to @grzesiek2010 has been reopened so I have a little...

I just ran into this with a text question followed by several minimal select one questions and it was pretty distracting. Ideally the latest question interacted with in a field...

> Entity properties with same name but different capitalization can't be created anymore I don't feel like we need to document this. The error is very clear and I don't...

We'll want to add a link to https://github.com/getodk/docs/pull/1859/files#diff-d1fd5d1b68bb4a3d5db94b2138eaf7ab19c8f8eeee5d9c69a6745a58d5e6eed1R330 Maybe you could plan on doing that after #1859 is merged either by pushing a commit here or doing another PR?

I added the link because I realized I wanted to change some wording too. The build will be broken but I think we can squash and merge after #1859 and...

This is the expected behavior as far as I know. The delete button is for deleting repeat instances. The confirmation dialog does seem pretty clear to me though I see...

This feels pretty niche and users haven't complained so let's close.

To support this, let's add `Scenario` method to load an existing instance. This could be an overload of `init` or something like `initWithInstance`. The instance will be passed in as...

@grzesiek2010 thanks for that explanation, it makes sense. Am I understanding correctly that currently we always include events for questions in a field list as long as they are visible...

> It sounds difficult Likely true. What about only including question events for questions in field lists that have had value changes AND omitting start and end time for those?...