Banditfuzz Branch Crashs. Three different inputs/error logs about stringfuzz HOT 8 OPEN

Fair. Fixed.

from stringfuzz.

Fix to Error 1 pushed to "bandit" branch. Pull it down and let me know.

Errors 2 and 3 seem to be parser issues.

from stringfuzz.

Error 2 is because "<" is not a string operator so it is not in the bandit's supported ops. Added a warning and ignoring those. Pushed to "bandit" branch.

from stringfuzz.

I'm confused, the command line interface says the following are operators: '=', '>', '<', '>=', '<=', 'Concat', 'Contains', 'At', 'Length', 'IndexOf', 'IndexOf2', 'PrefixOf', 'SuffixOf', 'Replace', 'ReInter', 'ReUnion', 'ReRange', 'RePlus', 'ReStar', 'ReConcat', 'Str2Re', 'InRegex', 'ToInt', 'FromInt', 'Substring'

from stringfuzz.

@FedericoAureliano heyoo, what do you think of merging banditfuzz into trunk, so you don't have to work on a branch? :)

Also, are there ways I can make it easier to write, say, only plugins (e.g. importing all files in a plugins folder, or looking at pip-installed packages)? That way you don't have to work on all of stringfuzz, and just have a repo with your plugin.

from stringfuzz.

Woah software engineering sensei teach me. I'm very keen for a way to write plugins that's independent (also for another project I'm working on). What's the best way to do it?

from stringfuzz.

@FedericoAureliano Heh, I'm far from a sensei. I'm barely passable!

The methods I'm considering:

1. Pass a --plugin path/to/plugin.py flag, and import the file at the path.
2. Pass a --plugin pip_package_name flag, and import the specified package by name.
3. Automatically run pip freeze in Stringfuzz, and import all things that start with a fixed string (e.g. stringfuzz-plugin-.*).
4. Automatically import everything inside the generators or transformers folders.

And then every such package would have to conform to an API, like its argument-parsing, its methods, etc.

What do you think of these? Do you have any ideas?

from stringfuzz.

I like 1/2 a lot. Handling the subparsers might be tricky though. I guess the plugin will have to define this stuff somewhere too. Maybe having the user provide a configuration file?

from stringfuzz.