These are chat archives for ushahidi/Community

29th
Jul 2015
Ushbot
@ushbot
Jul 29 2015 02:51 UTC
[Robbie Mackay, Ushahidi] I have a naming problem.. my import usecase has a "Transformer" interface for transforming a source record to something that can be imported.
[Robbie Mackay, Ushahidi] But we already have a 'DataTransformer' trait used for Entity classes.. which mostly just ensures the correct type for each field.
[Robbie Mackay, Ushahidi] @will any ideas on better naming conventions?
[Robbie Mackay, Ushahidi] .. although hopefully you're already asleep
[Will, Ushahidi] Transformer is more correct for the former usecase - is there any possibility of changing DataTransformer or is it too ingrained?
[Will, Ushahidi] Also any idea why I wouldn't be able to get rootscope in my directive, it's in my latest diff but it's failing for some reason
[Will, Ushahidi] the latter of the above seems like a TypeValidator or DataChecker
Ushbot
@ushbot
Jul 29 2015 02:57 UTC
[Robbie Mackay, Ushahidi] I agree DataTransformer is the wrong name. Its more like a Normalizer
[Robbie Mackay, Ushahidi] next problem is going to be figuring out a name for a 2nd layer of Usecases.. I can just keep using usecases.
[Robbie Mackay, Ushahidi] but its breaking out of the nice clean CRUD usecases.. and things like UsecaseFactory cease to work for every usecase
Ushbot
@ushbot
Jul 29 2015 03:46 UTC
[Will, Ushahidi] @Robbie I agree normalizer is a much better name, is the 2nd layer of usecases a pre-formatting or munging layer?
Ushbot
@ushbot
Jul 29 2015 03:51 UTC
[Robbie Mackay, Ushahidi] in some case. For import it does some data prep before hand: passing maps to the transformer, and loading files based on a filename or media id..
[Robbie Mackay, Ushahidi] theres often a need for something like a parsing layer
[Robbie Mackay, Ushahidi] I'm not really sure yet.. might just shelve that till it becomes more obvious
[Will, Ushahidi] that seems reasonable as a distinct layer for it could be a usecase preparer
[Will, Ushahidi] D899 is completed I believe but for some reason $rootscope is not functioning as expected though I've followed the existing the patterns. if you could poke it and see if I've missed something excruciatingly obvious and I'll fix it first thing in the morning.
night!
Ushbot
@ushbot
Jul 29 2015 04:02 UTC
[Robbie Mackay, Ushahidi] Alright thanks!
adambard1
@adambard1
Jul 29 2015 21:17 UTC
Almost certainly both already considered – 20) If desired, links shared in posts to be clickable? 21) Text in posts to be formattable (bold/italic etc)?
Ushbot
@ushbot
Jul 29 2015 21:44 UTC
[Robbie Mackay, Ushahidi] @adambard1 yup. We have markdown formatting on the main post content but thats all so far. Need to think about how to do that better with custom fields
[Robbie Mackay, Ushahidi] It probably won't make it into a 3.0 release but maybe shortly after
adambard1
@adambard1
Jul 29 2015 22:47 UTC
re 19) above, the problem seems to be associated with trying to use the '+' symbol in the category heading. Substituting the word 'over' lets the category be created.
Ushbot
@ushbot
Jul 29 2015 22:49 UTC
[Robbie Mackay, Ushahidi] ah that'd make sense.. though obviously you should have gotten better feedback than that
adambard1
@adambard1
Jul 29 2015 22:54 UTC
Other symbols are fine, (-/–) etc.