When automate was first laid out, we called the application of a specific use-case a "solution".
as in: A pattern describes a coding pattern, found in existing coebase. It is composed of one or more code templates, in some structure, supplemented with automation and constraints etc.
That pattern is then packaged up into a toolkit, and that toolkit is used "as a template" to create an instance of "use" of the toolkit. We called that instance of use, a "solution".
Recently (e948f2b) we changed the term "solution" to "draft".
The question is that now we are describing the concept as a "draft" it does not fit so well in all contexts.
The term "use-case" is a better term all up, but it's two words - which is its only con.
I believe that the term "usecase" is a better term in most contexts.
Should we use the term "use-case", stick with the term "draft" or use something else entirely?
When automate was first laid out, we called the application of a specific use-case a "solution".
as in: A pattern describes a coding pattern, found in existing coebase. It is composed of one or more code templates, in some structure, supplemented with automation and constraints etc.
That pattern is then packaged up into a toolkit, and that toolkit is used "as a template" to create an instance of "use" of the toolkit. We called that instance of use, a "solution".
Recently (e948f2b) we changed the term "solution" to "draft".
The question is that now we are describing the concept as a "draft" it does not fit so well in all contexts.
The term "use-case" is a better term all up, but it's two words - which is its only con.
I believe that the term "usecase" is a better term in most contexts.
Should we use the term "use-case", stick with the term "draft" or use something else entirely?