Is there something special(i.e. a design pattern being related) to a method named create()?
The case is, I often make some instances of objects (of the same class/prototype). These objects do not always already objects reflect a state in which they are complete yet. Potentially some initialization needs yet to be done to make them more completly initialized (which cannot be done in the constructor function/method) since for some reasons the information to do so might existing already. An alternative making of the objects once this information is available is made difficult since the objects already made are made available via references to other objects (even though some functionality is not yet possible because of the some missing initalization).
In order to have a way to complete the initialization of the object I would like to call a method
.create([...]) on the objects which should be a way for a second step completion of some of the objects initialization.
My interest is if related to this background is if this is a legitimate/reasonable course of action (i.e. to have some objects that may have different states of readyness; which are made into a "complete" state via a method - I thought to name that
Specifically I would of course like to know if there are for instance already patterns with standard method names for the described task (two-step initialization of objects) and also if the method name
.create[...] chosen in worst case conflicts with some existing pattern and would confuse readers of my code.