-
Notifications
You must be signed in to change notification settings - Fork 4
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
simpleterm creation #10
Comments
For no good reason, I believe. I suspect its just an artifact from the very first versions where groups were define by just titles and there was no support for | separator. When I added | separator, I did not update token formula. Probably normalized version of "value" would work fine. |
i am fine with "value" too and will implement it that way. done. @datakurre can you publish it on pypi? |
Thanks. I should be able to do release on Monday.
…On 29 Sep 2017, 15.21 +0300, Markus Hilbert ***@***.***>, wrote:
i am fine with "value" too and will implement it that way.
done.
@datakurre can you publish it on pypi?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@iham Released 2.2.1. Took some time to fix issues on test setup. |
https://github.com/collective/collective.roster/blob/master/src/collective/roster/behaviors/groups.py#L82
why is the token derived from group (which is a tuple ) instead of normalizing the title or the id?
i use "id_from_normalized_groupname | groupname" for the roster groups.
on testing the value of the checkboxes are value="normalized_groupname-normalized_groupname" which is redundant... and somewhat hard to test...
wouldn't it be nicer to just normalize the title (the second part of the group tuple) for the token or use the plain id (first part of tuple)?
i wouldn't mind, spending that time, if there are no problems i don't see.
regards, iham
The text was updated successfully, but these errors were encountered: