Open mcmc101001 opened 10 months ago
The UG clearly states that switching parameter order is not supported:
Might be something to consider implementing in future iterations of the product.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
It is unable to accept the command where elevation is brought forward, when there is no need to sequence the different tags, causing unnecessary trouble to users