Tag: Branch: Tree: ff436b6d52

edge

master

0.1.0

0.2.0

0.3.0

0.4.0

0.5.0

0.6.0

0.6.1

0.7.0

0.7.1

0.7.2

0.7.3

0.7.4

0.8.0

0.8.1

0.9.0

0.9.1

0.9.2

0.9.3

0.9.4

1.0.0

1.1.0

1.1.1

1.1.2-beta

1.1.3-beta

1.10.0

1.10.1

1.10.2

1.11.0

1.11.1

1.11.2

1.12.0

1.13.0

1.13.1

1.14.0

1.14.1

1.14.2

1.14.3

1.15.0

1.15.1

1.15.2

1.15.3

1.16.0

1.16.1

1.16.2

1.17.0

1.18.0

1.18.1

1.19.0

1.19.1

1.19.2

1.2.0

1.3.0-beta

1.3.1-beta

1.3.2-beta

1.4.0

1.5.0

1.6.0

1.6.1

1.6.2

1.6.3

1.7.0

1.8.0

1.9.0

latest

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'ff436b6d52'

${ noResults }

Commit Graph

4 Commits (ff436b6d52665df815033eab614d847777576754)

Author	SHA1	Message	Date
Alexis Degrugillier	d229216ccc	Split the search into values ... Before, the search was a single value. Now it is splited in chuncks when separated by spaces. Except if they are enclosed by single quotes or double quotes. For some reasons, the unit tests are working for both single and double quotes but the search box isn't. It is working only with single quotes. We need to investigate the reason of this behavior. See #823	10 years ago
Alexis Degrugillier	50b6a02578	Add search default raw value ... Before, the default value was undefined. Now it always has a value even when no value is provided.	10 years ago
Alexis Degrugillier	964e67d4a4	Add a test to verify if the search input is stored correctly	10 years ago
Alexis Degrugillier	f30ded2f86	Extract the search code from the context ... I figured that the code for the search could be extracted from the context to have separation of concern. It supports multiple keywords. It suports also multiple tag keywords.	10 years ago