Search for multiple tags in DHTML version #283
Comments
|
@albertdabrowski could you please enhance this description? One of the questions I have is: |
|
In our case we would like to have "OR", but I think "AND" would be also valuable. So I think in this case it's a matter of search capability. Do we want to keep it simple or more like for example search in JIRA? |
|
OR would mean that Right? I'm happy you said OR, because the OR behaviour is consistent with many other search-by-property search definitions that treat different properties as AND criteria, and different values of the same property as OR criteria. I have to admit I have no experience with JIRA. |
|
@aaronjrich would you have a moment to get in touch with me? I'd like to ask you a few questions about the DHTML version, with the goal that I am able to extend it myself. I feel bad about having to bother you every time something with the DHTML version comes up. |
|
@dirkrombauts, sorry about not getting back sooner. Let me know what time works for you. |
|
@aaronjrich tomorrow (19 February) in the forenoon would work for me (for example). I'm in GMT+2, I don't know which timezone you are in ... BTW, if you are on gitter, you can send me a message there, that's perhaps easier than filling up this feature request. |
|
Apparently gitter is blocked here where I work. Is there another way to proceed with this? |
|
You can email me at dirk dot rombauts at picklesdoc dot com . Does Skype work at your workplace? |
* Fix failing tests by removing overspecification * Untabify * Ensure description of feature is never null, fixes crashes of word and excel generation * Unit test * SpecFlow conformant name mapping * Implement name mapping in nunit signature builder more conformant to SpecFlows name generation logic wrt. to special characters * Unit tests for special character handling * Basic comments handling (#311) * basic comment handling * add excel handling * cleanup * clean up * fix tests * handle comments after the last step of a scenario * clean up * codestyle clean up * codestyle clean up * add test for mapper on comments * clean up * adding mapper tests on comments and location + more clean up * Update Nuget packages (and small fixes) (#310) * Update-Package SpecFlow * Update-Package Nunit * ExpectedException is obsolete in nunit3 * Update-Package System.IO.Abstractions.* * Refactor CurrentScenarioContext to be instance-based and to be injected * Update-Package MahApps.Metro * Update-Package AutoMapper * Update-Package Newtonsoft.Json * Remove IKVM assembly binding redirects * Do not use ScenarioContext.Current * tweak gitignore * Update GhostDoc file * Downgrade Automapper to last known good version * Exclude test project from test coverage * Edit applicationhost.config * Added support for multiple tags when searching (issue #283) (#319) * Use Gherkin 4 parser (#322) * Update-Package Gherkin * tweak applicationhost.config * Factory creates a GherkinDocument now * The parser now returns a GherkinDocument * Map a GherkinDocument to a Feature * Use new icon (#323) * Use new icon * Use a big png file with the new logo * Use the new .png file in the .nuspec files * Use visual studio 2015 * Version bump to 2.6.0 * Update change log
|
Released in version 2.6.0 |
|
Great, thanks for the efforts. Appreciate, |
Currently the DHTML version allows to search for only one tag at a time. In larger specifications, there are often many tags used in specific combinations. It would be beneficial if we could search for multiple tags.
The text was updated successfully, but these errors were encountered: