Tag: Branch: Tree: 2af3abc89e

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 '2af3abc89e'

${ noResults }

Commit Graph

2 Commits (2af3abc89e56af75c38caf5e8071b3cd09bedba8)

Author	SHA1	Message	Date
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
Alexis Degrugillier	4bb8548ecc	Add a way to parse search string to extract keywords ... This feature is not in use at the moment, but it will be handy to reorganize the query building process. It allows to have more than one keyword in the search box. Full tests are available as well. It probably needs a refactoring later, but I think this is the first step to make the application full object oriented and testable.	10 years ago