We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As seen with @northox and @jfrioux https://gitter.im/floraison/flor?at=5fbfb55f846eed6b67ae2bf2
Reproduced in https://github.com/jmettraux/issue_flor_hook_20201126
It seems hooks with point: return are not triggered.
point: return
The workaround is to write point: "return" or point: 'return'.
point: "return"
point: 'return'
[ { point: execute, consumed: true, nid: '0', require: 'pollen/pollen.rb', class: 'LaunchedPollenHook' }, { point: return, consumed: true, require: 'pollen/pollen.rb', class: 'ReturnedPollenHook' }, { point: terminated, consumed: true, require: 'pollen/pollen.rb', class: 'TerminatedPollenHook' }, { point: failed, consumed: true, require: 'pollen/pollen.rb', class: 'FailedPollenHook' }, ]
Probably the point gets evaluated to an empty string (and never matches).
The text was updated successfully, but these errors were encountered:
Rework conf at the end of ConfExecutor, gh-36
465d4ed
@northox @jfrioux I think the commit above solves it. Please tell me if not. Thanks again for reporting that!
Sorry, something went wrong.
Quote points to avoid issues with reserved words and add a note to RE…
db0c7be
…ADME. Ref: floraison/flor#36
@jfrioux wrote in floraison/pollen#5 :
Though, just tested with commit 465d4ed, on Ruby 2.3.8 and 2.6.6 and the issue remains when return is unquoted.
Reopening...
jmettraux
No branches or pull requests
As seen with @northox and @jfrioux https://gitter.im/floraison/flor?at=5fbfb55f846eed6b67ae2bf2
Reproduced in https://github.com/jmettraux/issue_flor_hook_20201126
It seems hooks with
point: return
are not triggered.The workaround is to write
point: "return"
orpoint: 'return'
.Probably the point gets evaluated to an empty string (and never matches).
The text was updated successfully, but these errors were encountered: