Decision on implicit pre defined elements? #133
Description
Right now, some of the functions of the s2dm tools rely on predefined elements (i.e., graphql files) that are defined in the s2dm repo. This is however implicit and not straight forward for someone who is trying to run the commands on his own models. For example #131 indicates that is was unclear what to pass to the command as parameter.
User passed the final composed schema, resulting in multiple errors due to duplicated elements. While the actual expected argument parameter was the path to the schema files before composition.
The question is whether it makes sense that the s2dm repo only offers the tools, functions, etc. but not any pre defined elements that might cause ambiguous functionality....