Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / samuel-ziegler/vitest-cucumber-plugin issues and pull requests
#33 - Plugin can't parse a `.feature` file
Issue -
State: open - Opened by matthew-dean 3 months ago
- 1 comment
#32 - Auto resolve other extensions from vite config file
Pull Request -
State: open - Opened by haikyuu 12 months ago
#31 - Allow circular data structures in state (fixes #22)
Pull Request -
State: closed - Opened by joakimbeng about 1 year ago
- 1 comment
#30 - Make the step definitions glob pattern configurable
Pull Request -
State: open - Opened by joakimbeng about 1 year ago
- 3 comments
#29 - Add support for TypeScript and async steps
Pull Request -
State: open - Opened by joakimbeng about 1 year ago
- 8 comments
#28 - Log error and state when steps throw error
Issue -
State: open - Opened by samuel-ziegler about 1 year ago
#26 - Better error message when JS files fail to import
Issue -
State: open - Opened by samuel-ziegler about 1 year ago
#25 - The parser fails to parse when an @ symbol is in a data table
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#24 - Create clean dist package
Issue -
State: open - Opened by samuel-ziegler about 1 year ago
#23 - Better way to communicate JS errors when importing step files
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#22 - Handle circular references in the state object better
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
- 1 comment
#21 - Provide code snippet for steps without step definitions
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#19 - Allow step/support/features files to be anywhere under features directory
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#17 - Increase test coverage
Issue -
State: open - Opened by samuel-ziegler about 1 year ago
#16 - Make info log level useful for users
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#15 - I18n support
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
- 1 comment
#14 - Add basic example to README
Issue -
State: open - Opened by samuel-ziegler about 1 year ago
#13 - Define methodology for chosing tags via vitest command line
Issue -
State: open - Opened by samuel-ziegler about 1 year ago
- 1 comment
#12 - Implement Cucumber Hooks methods
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#11 - Remove need to manually generate nearley parser
Issue -
State: open - Opened by samuel-ziegler about 1 year ago
- 1 comment
#10 - Document Data Table Given/Then/When argument
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#9 - Add to npm registry
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#8 - Have Vitest watch step definition files
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#7 - Document configuration options
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#6 - API documentation
Issue -
State: open - Opened by samuel-ziegler about 1 year ago
#5 - Add boolean expression suport for tag filtering
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#4 - Add escaping support for Data Tables
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#3 - Implement Doc strings
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#2 - Implement Rule keyword
Issue -
State: closed - Opened by samuel-ziegler about 1 year ago
#1 - Typescript support?
Issue -
State: open - Opened by thelinuxlich about 1 year ago
- 2 comments