Won't Do
Details
Assignee
UnassignedUnassignedReporter
Mike TaylorMike TaylorLabels
Priority
P4TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter
Mike Taylor
Mike TaylorLabels
Priority
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created March 27, 2018 at 2:14 PM
Updated August 24, 2021 at 12:25 AM
Resolved July 9, 2019 at 7:11 PM
As app developers like Frontside continue to diverge from the way we're building our own Stripes apps, and we find ourselves sometimes needing to give guidance, we need to differentiate in our own minds (and in docs) between
A. Here is the Stripes-module contract. Do ye these things
B. Here are some facilities we provide to help you fulfil A.
A given app developer may be making bad decisions (to our mind) in ignoring B, but they are fully within their rights. But they must do A, and that's what our communication with them needs to emphasize.
To facilitate this, we need either a new, terse, document simply listing the parts of the Stripes API that are in each category; or, perhaps simple a new section in the Stripes Developer Guide.