the structure of EO directories is not clear
Currently the process is described in EO maven plugin. It would be good to extend the description with the input/output folders structure for each step.
@yegor256 do you find this appropriate?
@mximp yes, definitely, would be nice to extent the README
@Graur fix this please (or delegate)
@levBagryansky please, help to improve README.md file
@levBagryansky It would nice to have description of target/eo folder structure as well as what files are consumed/produced by each compilation step.
@mximp so I need to imrove README.md in eo/eo-parser? How can I understand what is going on there?
@levBagryansky I'd say eo-maven-plugin/readme.md. You could run compilation, check target/eo/ and find how it's populated/used in the plugin code.
@mximp maybe it would be better to leave a link to the post to avoid repeating?
@levBagryansky The post explains what the phases are but doesn't specify exact input and output. I believe some addition is required. I've tried to accumulate the info here as another blog post: https://github.com/mximp/news.eolang.org/commit/cc01abcc9a81143de3156d353aacd11db6bdce05. But the format is not very readable. Maybe you could think of another representation.
@levBagryansky What's up with this issue?
@mximp we still have this issue?
@Graur anything left here?
@mximp @yegor256 Yes, we still have this issue @MikhailLipanin Can you help us here?
@Graur Do we still need to solve that?
@volodya-lombrozo I believe we should ask @mximp about it. Since we have short description in eo-maven-plugin/README.md. But is it enough?
@Graur @volodya-lombrozo The idea was to add more detailed information about actions on files during compilation. The attempt was made here, but as I mentioned it's quite unreadable.
We could at least add a folder structure of EO plugin here: https://github.com/objectionary/eo/tree/master/eo-maven-plugin/README.md.
@Graur I can take care of it.
@volodya-lombrozo Sure, go ahead