Skip to content

converting rails engine to rails gem, and development #2

@alvinsj

Description

@alvinsj

I found that your viewmodel pattern is nice and helpful for what I am currently working on. However, I found that often times I need to customize the views(e.g. filter/table) to display the reports, so I made the views generator in order to copy the default views to the project. In my opinion, I think this will happen very often, and maybe too often that we can actually just make it as part of setting up the gem.

For report generation, I think it's hard to make that one gem fits all. Rather than coding a full featured, highly customizable rails engine, maybe focusing on providing modules/parts/helpers/tools might be more feasible. That is which I found the potential of this gem, make something easily fit into any design pattern.

Of course, maybe this is only my preference/opinion, let me know about your thoughts. I made another branch and already converted it to a rails gem. I was thinking to make pull request, but I think better check with you guys on this. or otherwise I will use my fork to improve some feature after that. Cheers.

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