I’m following the instructions to create a library for the first time.
My scenario is that we had this project that was used for specific tasks.
Now we have a very similar requirement that only has a few minor diferences. We can replicate the project and then do the needed modifications there. The problem is that when we have to implement a new feature or correct a bug we will have to replicat the same in both projects, so we don’t want them separated.
Another option would be to save our current existing, original project in its own workflow, then parametrizing every specific subtask or piece of code that belonged to the original project, then call it with the proper parameters depending on it being subproject A or subproject B.
The problem here is that I can’t think of a different way ather than requiring some user interaction, like asking “What kind of documents do you want to generate? Type A or type B?”. And we want to avoid that, because or goal is to fully unnatend everything in the mid term.
So the option I would go for, after googling and discovering it, is creating a library and keeping two independent projects, making use of the common library, that we will call at our will.
My specific question is: every piece o documentation, tutorials and/or forum posts seem to imply that any library must be creted from scratch.
Isn’t there a way to create a library from a specific, existing project?