-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SessionSeries requirements for eventSchedule and subEvent should be forgiving #390
Comments
Second this! Worth noting that Test Suite has a workaround for this exact reason (here), which is not ideal at all. The BookingSystem.AspNetCore reference implementation within OpenActive.Server.NET outputs SessionSeries which fail this rule (but shouldn't as it has split feeds). We at imin also have a workaround in our code for this I think that, until this is fixed, more workarounds are going to show up, adding tech debt to the general ecosystem. It's also the recommended approach (in the dev docs) to use split feeds, so this rule is not necessarily very useful It's not obvious how to solve this so shall we start iterating on a possible solution, @nickevansuk ? As some starter-for-10 proposals:
To clarify for any future searches, we're specifically talking about the |
SessionSeries requirements for eventSchdule and subEvent should be forgiving for split-feed implementations, as currently if the validator validates only one half of the split it is not possible to determine whether the
subEvent
may be defined in the other halfThe text was updated successfully, but these errors were encountered: