Skip to content

Future of prooph cli #19

@codeliner

Description

@codeliner

From the chat:

Guys, last weekend I've started small project - https://github.com/mmp4k/proophgen - do you think has it sense?
cli tool to generate boilerplates

Tomáš Čížek @tomcizek 16:17
hey that sounds cool, but cannot find any docs to see how those generated files looks like

Sascha-Oliver Prolic @prolic 16:17
@mmp4k check https://github.com/proophsoftware/prooph-cli

Alexander Miertsch @codeliner 16:17
@mmp4k We did the same a while ago: https://github.com/proophsoftware/prooph-cli
But we had not enough time to make it stable

Sascha-Oliver Prolic @prolic 16:17
if you have improvements, you can improve from there

Alexander Miertsch @codeliner 16:18
@prolic was faster

Sascha-Oliver Prolic @prolic 16:18
@codeliner maybe we can move this repo to prooph organization, so it's more visible
and others can provide PR's to improve it

Alexander Miertsch @codeliner 16:19
yeah, we can do that but it did not see an update since last year 😃

Marcin @mmp4k 16:19
hm, good to know, I will check it weekend, maybe there is a way to merge that two projects

Alexander Miertsch @codeliner 16:19
@mmp4k 👍

Tomáš Čížek @tomcizek 16:19
@prolic haha I didnt knew about it, gonna look at that

Marcin @mmp4k 16:21
@tomcizek check there: https://github.com/mmp4k/proophgen_result

Alexander Miertsch @codeliner 16:21
there are some problems that need to be solved:
prooph is not a framework, so there is no recommended folder structure or naming convention
the cli commands have to be very flexible, but this makes to tool hard to use

Sascha-Oliver Prolic @prolic 16:21
community pr's would be great 😀 we are only a small core-team and cannot cover all places at once

Alexander Miertsch @codeliner 16:24
so the cli tool needs some kind of basic configuration to tell it where commands, events, handlers, listeners, etc. live and how they are named.
It is also recommended to work with a custom message factory and custom message names instead of using the PHP class names (tutorial part for that will be added soon). The cli tool needs to take that into account and ideally provides a way to setup such a custom naming strategy.

Sascha-Oliver Prolic @prolic 16:25
@codeliner put all this extra info in a github issue, so it's not lost in chat

Alexander Miertsch @codeliner 16:25
yep

Sascha-Oliver Prolic @prolic 16:25
thanks

Tomáš Čížek @tomcizek 16:25
i like that idea of configurating in yaml how those files will be generated... But it is not just about paths and folder structure

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions