Appropriate values for created_at
and upated_at
for a new app?
#4427
-
Love to see the audit fields merged and looking forward to the new app view! I'm in the midst of working on an app config with a drsaft PR on the main repo, and it's now failing CI because I don't have those fields. From the modicum of tracking the feature discussions I've been doing I gather these will be updated by the store / CI code. I can grab the "dummy" values that are in #4425, and i assume those will work, but is that what new app authors should do? I'm happy to take a stab at updating the docs repo with the new info once i understand it better - i have a local branch with some typo fixes that seemed too trivial to PR on its own that I could include them in (although it'll be a few days most likely). |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
@meienberger nico if you can explain please :) Thanks |
Beta Was this translation helpful? Give feedback.
-
Hello, thanks for asking. You can check out the reference config.json guide which explains how to generate these values. I bet we could improve the CI to automatically add it tho |
Beta Was this translation helpful? Give feedback.
-
hah that docs update snuck in after i posted the question and matches my expectations. |
Beta Was this translation helpful? Give feedback.
Hello, thanks for asking. You can check out the reference config.json guide which explains how to generate these values. I bet we could improve the CI to automatically add it tho