-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inserting an activity name starting with a decimal number causes activity name to be overwritten #270
Comments
Thanks for the detailed report, with steps to reproduce ! This is fixed in current master (tested with 79db77f). Leaving open with the hamster-applet label (for the 1.04 version) |
Probably related so noting this here: in my imported hamster.db I have lots of activities that start with an issue number prefixed by #. These are all coming up blank in the display and when exported. I was able to workaround the issue by replacing the # with a text string in the db. |
@pwhipp Thanks for the report, but could you please open a new issue, |
Closing, since the main issue is thought to be solved in the development version. |
This PR reverts the use of a double comma to indicate the start of the description, a breaking change introduced in Hamster 3.0, back to the previous use of a single comma, as discussed in projecthamster#657. Likewise, the double comma needed before tags, in the case of descriptions containing the #hash pattern, is also reverted to the use of a single comma. This change requires two restrictions to the parsing rules. Firstly, no comma is allowed in the activity name (projecthamster#270). Secondly, tags may not be separated by a comma when entered on the commandline (ie. just use `#tag1 #tag2`, not `#tag1, #tag2`).
This PR reverts the use of a double comma to indicate the start of the description, a breaking change introduced in Hamster 3.0, back to the previous use of a single comma, as discussed in projecthamster#657. Likewise, the double comma needed before tags, in the case of descriptions containing the #hash pattern, is also reverted to the use of a single comma. This change requires two restrictions to the parsing rules. Firstly, no comma is allowed in the activity name (projecthamster#270). Secondly, tags may not be separated by a comma when entered on the commandline (ie. just use `#tag1 #tag2`, not `#tag1, #tag2`).
Fails on both 1.04 and master branch
Steps to reproduce:
Expected result
Actual result:
The text was updated successfully, but these errors were encountered: