40 lines
2.2 KiB
Markdown
40 lines
2.2 KiB
Markdown
# TODO 1: After Parse callback [COMPLETED]
|
|
Currently interdependent arguments are a problem. In the current version we are handling them as closures.
|
|
We create two stateful actions who are taking the state from the close over of the lambda. This is a little hacky/ugly.
|
|
To fix this we could have a callback/on_parse_done event. An example usage could be;
|
|
```cpp
|
|
parser.after_parse([&parser]() {
|
|
auto grep_val = parser.get_optional<std::string>("grep");
|
|
auto file_val = parser.get_optional<std::string>("file");
|
|
|
|
if (grep_val && file_val) {
|
|
grep(*grep_val, *file_val);
|
|
} else if (grep_val) {
|
|
std::cerr << "grep requires file\n";
|
|
}
|
|
});
|
|
```
|
|
|
|
After handle_parse(...) ends, we can call the on_parse_done callbacks. But this requires two things;
|
|
1. Storable arguments. Those would be not actions, but stored values. So you could get them later on in the callback or somewhere else.
|
|
2. The on_parse_done callbacks should be called after all actions are invoked. But we should make this a toggle, so the callback only gets executed if the user explicitly wants it to be called. By default we would enable it.
|
|
|
|
## Self reminder, implement this feature. It'd be helpful.
|
|
|
|
### Update: 6 Oct. 2025
|
|
We now have storable arguments. Now we need to implement the on_parse_done callbacks, to achieve this feature.
|
|
|
|
Also the run after complete events are implemented.
|
|
|
|
# TODO 2: Positional arguments
|
|
Positional arguments are arguments that are not prefixed with a dash. They are usually the arguments that are passed to the program.
|
|
For example, in the command `grep "pattern" file.txt`, "pattern" and "file.txt" are positional arguments.
|
|
|
|
# TODO 3: Separate headers from implementations
|
|
Right now whole project is header only. Header only so far is fine but to avoid issues later on, it's better if we separate them.
|
|
|
|
# TODO 4: Configure CMAKE
|
|
Configure CMAKE to ensure the library can be built as a library and can be installed via CMAKE. This should make adoptation of this to existing projects easier with less headache.
|
|
|
|
# TODO 5: Display help
|
|
Display help doesn't reflect the conventions right now. Also it should come automatically, and should be allowed to overriden by user. |