Is your feature request related to a problem? Please describe.
A user has reported an issue where the current numbering system for runs doesn't make sense to them. They suggested that having the run number as the name would be more intuitive and practical.
Describe the solution you'd like
I propose that the parser automatically initializes the "pretty_name" field as "Run #x", where x is a sequentially increasing number starting from 1. This would provide a clear and consistent naming convention for runs, enhancing organization and identification.
Describe alternatives you've considered
N/A.
Additional context
It's important to note that this numbering system should continue seamlessly even if the parser is restarted. One way to achieve this could be by counting the number of existing files and continuing from that count. Please be careful when implementing this, you cannot fetch the last modified file because users can edit any run's name through the app.
Is your feature request related to a problem? Please describe. A user has reported an issue where the current numbering system for runs doesn't make sense to them. They suggested that having the run number as the name would be more intuitive and practical.
Describe the solution you'd like I propose that the parser automatically initializes the "pretty_name" field as "Run #x", where x is a sequentially increasing number starting from 1. This would provide a clear and consistent naming convention for runs, enhancing organization and identification.
Describe alternatives you've considered N/A.
Additional context It's important to note that this numbering system should continue seamlessly even if the parser is restarted. One way to achieve this could be by counting the number of existing files and continuing from that count. Please be careful when implementing this, you cannot fetch the last modified file because users can edit any run's name through the app.