To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.
name: calendar-tidy
description: A command-line utility to cleanup specified events from Google Calendar.
reasoning: write access to $HOME/.config/calendar-tidy for storing configuration information
I’ve actually been using this snap for some time without this interface even defined in my snapcraft.yaml and it worked fine - I think because the file had already been created by a pre-snap version of the application.
No, the reason that this works is because confined snaps simply point their HOME variable to SNAP_USER_DATA at runtime, so it will simply create and use $SNAP_USER_DATA/.config/calendar-tidy by default…
Using a personal-files interface like this to write to the real HOME is usually only relevant when you expect that a user switches from a non snapped version of the app to a snap one and you want to import the existing data… or if you expect other third party apps to access the config data in your homedir directly.
Normally putting the configuration in the snap specific folders is enough without the need for a personal-files interface
+2 for, 0 against granting calendar-tidy auto-connection to the requested personal-files interface. The publisher is vetted. This is now live.
Next revision of the snap declaring the requested plug should pass automatic review. Please remember that according to the naming convention for personal-files interfaces, the plug should be named dot-config-calendar-tidy
