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 your feature request related to a problem? Please describe.
When creating templates in KeePassDX using a key:value form, there is no way to include a key:value pair within another key:value entry. For example, I am unable to use a nested structure like text {default:inside_key:value} because the inner colon causes parsing issues. This limitation makes it difficult to store values that themselves contain a colon, which is common in structured data formats.
Describe the solution you'd like
I would like KeePassDX to support escaping colons inside values or provide an option to skip parsing colons within a key:value pair. For example, allowing something like text {default:inside_key\:value}, where the colon in the value is treated as part of the string and not as a delimiter. This would allow users to store more complex values, such as nested key-value data, within a single entry.
Describe alternatives you've considered
Currently, an alternative is to replace colons with other characters (such as underscores or dashes), but this is not ideal when the colon is required by the format of the stored data. Another approach is manually editing the data after template generation, but this is inefficient and increases the risk of errors.
Additional context
This feature would improve flexibility in storing structured data within KeePassDX entries, especially for users who need to manage complex configurations that include colons in their values.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When creating templates in KeePassDX using a key:value form, there is no way to include a key:value pair within another key:value entry. For example, I am unable to use a nested structure like
text {default:inside_key:value}
because the inner colon causes parsing issues. This limitation makes it difficult to store values that themselves contain a colon, which is common in structured data formats.Describe the solution you'd like
I would like KeePassDX to support escaping colons inside values or provide an option to skip parsing colons within a key:value pair. For example, allowing something like
text {default:inside_key\:value}
, where the colon in the value is treated as part of the string and not as a delimiter. This would allow users to store more complex values, such as nested key-value data, within a single entry.Describe alternatives you've considered
Currently, an alternative is to replace colons with other characters (such as underscores or dashes), but this is not ideal when the colon is required by the format of the stored data. Another approach is manually editing the data after template generation, but this is inefficient and increases the risk of errors.
Additional context
This feature would improve flexibility in storing structured data within KeePassDX entries, especially for users who need to manage complex configurations that include colons in their values.
The text was updated successfully, but these errors were encountered: