Stepan Anchugov
Stepan Anchugov
Maybe this should be opened against the crawler component, but this looks like an application-wide feature. We could trigger application-wide events during the crawler's lifecycle when a request is initiated,...
Looks like the note about all connections being made to `localhost:6379` is not relevant anymore.
Transitions require an array as `from` option, but strings were passed in the sample instead.
Perhaps explicitly stating that the bundle is already included within the base package is worth noting, as this is not so typical (usually you'd have to require the bundle separately).
| Q | A | ---------------- | ----- | Bug report? | yes | Feature request? | no | BC Break report? | no | RFC? | no | Version/Branch...
| Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass?...
| Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass?...
| Q | A | ---------------- | ----- | Bug report? | yes | Feature request? | no | BC Break report? | no | RFC? | no | Version/Branch...
| Q | A | ---------------- | ----- | Bug report? | no | Feature request? | no | BC Break report? | no | RFC? | no | Version/Branch...
I'm developing a bundle that gives access to some models which should be persisted differently depending on how my bundle is configured. For instance, models in my bundle can conditionally...