"your module" #4384

jasenfici@gmail.com created 2 years ago

Hi all,

One of the problems we are spending an inordinate amount of time with is in reference to documentation. In my example I will reference the Text Templating Razor document since that is what we are struggling with at the moment (https://docs.abp.io/en/abp/latest/Text-Templating-Razor)

As most, we are using a scaffolded application (in our case, generated with abp-suite).

However, when we go to look up and follow instructions on how to implement modules, the documentation makes frequent references to the term "your module". This is an incredibly generic term and our team spends a lot of time trying to figure out what the abp team means by that in reference to the entire solution, as there are many many "modules" within a single solution. I know abp has a specific definition of a "module" but in the scope of an entire pre-built solution, the term is just not specific enough.

We have currently spent days trying to figure out how to simply follow the directions on the TextTemplating documentation, with aspects of it still not working, as we are constantly left guessing exactly WHERE some section of code needs to go. In the Text-Templating-Razor documentation alone, there are five references to "your module". Maybe we are completely dumb, or maybe we have missed some greater more abstract implication to that term, but in either case we could use some clarity.

Please don't say look at the demo's either. We have. They are all implemented in much small bite-size (and most the time single-module) demonstrations, which is great for seeing things in action, but not helpful when trying to simply follow the docs on the standard solution.

The attached screenshot is a sample. There are 4 references to "your module", plus no direct reference on which module both of those "ConfigureServices" calls are referencing.

Thanks! (hoping a request for document clarity doesn't count towards our tickets ;-)

1 Answer(s)