I don't agree.  When the you format your commit messages it adds it to the 
issue automatically.  I'm not going to post a duplicate message for it.


-Mark

-----Original Message-----
From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash 
Muppirala
Sent: Thursday, April 28, 2016 7:51 PM
To: dev@flex.apache.org; Mark Kessler
Subject: Re: [jira] [Resolved] (FLEX-35082) moveIndexFindRow doesn't accept 
integer values

The general practice is to add the commit sha as a comment when closing a
ticket.  It will make things easier to track.

Thanks,
Om

On Thu, Apr 28, 2016 at 4:39 PM, Mark Kessler (JIRA) <j...@apache.org>
wrote:

>
>      [
> https://issues.apache.org/jira/browse/FLEX-35082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Mark Kessler resolved FLEX-35082.
> ---------------------------------
>        Resolution: Fixed
>     Fix Version/s: Apache Flex 4.16.0
>
> > moveIndexFindRow doesn't accept integer values
> > ----------------------------------------------
> >
> >                 Key: FLEX-35082
> >                 URL: https://issues.apache.org/jira/browse/FLEX-35082
> >             Project: Apache Flex
> >          Issue Type: Bug
> >          Components: Spark: List
> >    Affects Versions: Apache Flex 4.14.1
> >            Reporter: Dany Dhondt
> >            Assignee: Mark Kessler
> >            Priority: Minor
> >             Fix For: Apache Flex 4.16.0
> >
> >         Attachments: Main.mxml
> >
> >
> > This method has the following signature:
> > public function moveIndexFindRow(field:String, value:String,
> startingIndex:int = 0, patternType:String = RegExPatterns.EXACT):Boolean
> > When a dataProvider object with key 'field' has a 'value' of other than
> String, the method fails
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Reply via email to