You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Zencode parser returning Zencode pattern not found could also try and match a list of Restroom-mw statements. The statements are all contained in files .ts or .js in a structure like this :
const actions = {
CONNECT: "I have a valid redis connection on {}",
WRITE: "write all data as a hash into redis",
WRITE_WITH_KEY: "write all data into redis under the key {}",
};
Therefore the list can be generated with a script and the script put in CI
The text was updated successfully, but these errors were encountered:
It can be a rule unknown observe restroom where in DATA the caller also passes a JSON array named restroom containing statements formatted as Zencode (with single quotes '' in place of {}), then the ZEN.parser() function should be modified to observe with a simple match these statements before producing an error.
that I have a PR from 7 months waiting to be merged in dyne/restroom-mw#206 that exposes all the sentences.
I was lazy, need to write tests and also a small refactorin to include them in cliroom. Will do that, as soon as it's merged, you can ask the list of all the restroom sentences, from any restroom instance under http://restroom-instance-address/sids
The Zencode parser returning Zencode pattern not found could also try and match a list of Restroom-mw statements. The statements are all contained in files .ts or .js in a structure like this :
Therefore the list can be generated with a script and the script put in CI
The text was updated successfully, but these errors were encountered: