You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it necessary that the passport sections be consecutively numbered? If so, this could cause some tedium when removing an early entry in a long list of passports and having to -1 most of the sections.
The text was updated successfully, but these errors were encountered:
That's a good point - and to be honest I didn't think about a scenario where one would remove an early passport entry ^^. So I can't give you an answer right off the bat. I'll check this during the next couple of days. However I thought about replacing the numbering with the service name instead (e.g. [passport "github"]) anyways, but wasn't quite convinced to go that route.
I figured it isn't really an issue because the numbering is used as an identifier to avoid duplicates inside the configfile. While parsing the passports get enumerated anyways. What happens if a user would remove a passport is that the numbering on the selection dialog does not match the identifier inside the configfile anymore. But as I said that doesn't have any impact on the result. However it's not a good solution.
Is it necessary that the passport sections be consecutively numbered? If so, this could cause some tedium when removing an early entry in a long list of passports and having to -1 most of the sections.
The text was updated successfully, but these errors were encountered: