Re: [galaxy-dev] Full path through API display.py
Thanks Dannon. I was actually in a hurry so I poke around and found what I think is the right place to tie this in. In function get_api_value in lib/galaxy/model/__init__.py line 1159: rval = dict( id = hda.id, model_class = self.__class__.__name__, name = hda.name, deleted = hda.deleted, visible = hda.visible, state = hda.state, + file_name = hda.file_name, file_size = int( hda.get_size() ), data_type = hda.ext, genome_build = hda.dbkey, misc_info = hda.info, misc_blurb = hda.blurb ) Would it be helpful if I submit a pull request for this? Cause I was wondering if for changes so simple as this one, a pull request from a third party introduces more overhead than help. On Tue, May 1, 2012 at 3:05 PM, Dannon Baker dannonba...@me.com wrote: Sure, good idea. I'll tie it in. -Dannon On May 1, 2012, at 3:03 PM, Carlos Borroto wrote: Hi, Recently Full Path display was added as an option. I was wondering if this information could also be available when accessing a dataset information through the API. Thanks, Carlos ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] Full path through API display.py
Yep, that's the right place to put it. And you'll never hear me suggest someone *not* send in a pull request, so go for it :) -Dannon On May 2, 2012, at 3:08 PM, Carlos Borroto wrote: Thanks Dannon. I was actually in a hurry so I poke around and found what I think is the right place to tie this in. In function get_api_value in lib/galaxy/model/__init__.py line 1159: rval = dict( id = hda.id, model_class = self.__class__.__name__, name = hda.name, deleted = hda.deleted, visible = hda.visible, state = hda.state, + file_name = hda.file_name, file_size = int( hda.get_size() ), data_type = hda.ext, genome_build = hda.dbkey, misc_info = hda.info, misc_blurb = hda.blurb ) Would it be helpful if I submit a pull request for this? Cause I was wondering if for changes so simple as this one, a pull request from a third party introduces more overhead than help. On Tue, May 1, 2012 at 3:05 PM, Dannon Baker dannonba...@me.com wrote: Sure, good idea. I'll tie it in. -Dannon On May 1, 2012, at 3:03 PM, Carlos Borroto wrote: Hi, Recently Full Path display was added as an option. I was wondering if this information could also be available when accessing a dataset information through the API. Thanks, Carlos ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] Full path through API display.py
Done!. On Wed, May 2, 2012 at 4:35 PM, Dannon Baker dannonba...@me.com wrote: Yep, that's the right place to put it. And you'll never hear me suggest someone *not* send in a pull request, so go for it :) -Dannon On May 2, 2012, at 3:08 PM, Carlos Borroto wrote: Thanks Dannon. I was actually in a hurry so I poke around and found what I think is the right place to tie this in. In function get_api_value in lib/galaxy/model/__init__.py line 1159: rval = dict( id = hda.id, model_class = self.__class__.__name__, name = hda.name, deleted = hda.deleted, visible = hda.visible, state = hda.state, + file_name = hda.file_name, file_size = int( hda.get_size() ), data_type = hda.ext, genome_build = hda.dbkey, misc_info = hda.info, misc_blurb = hda.blurb ) Would it be helpful if I submit a pull request for this? Cause I was wondering if for changes so simple as this one, a pull request from a third party introduces more overhead than help. On Tue, May 1, 2012 at 3:05 PM, Dannon Baker dannonba...@me.com wrote: Sure, good idea. I'll tie it in. -Dannon On May 1, 2012, at 3:03 PM, Carlos Borroto wrote: Hi, Recently Full Path display was added as an option. I was wondering if this information could also be available when accessing a dataset information through the API. Thanks, Carlos ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
[galaxy-dev] Full path through API display.py
Hi, Recently Full Path display was added as an option. I was wondering if this information could also be available when accessing a dataset information through the API. Thanks, Carlos ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] Full path through API display.py
Sure, good idea. I'll tie it in. -Dannon On May 1, 2012, at 3:03 PM, Carlos Borroto wrote: Hi, Recently Full Path display was added as an option. I was wondering if this information could also be available when accessing a dataset information through the API. Thanks, Carlos ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
