Skip to content
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

feat: elaborate TODOs #227

Merged
merged 4 commits into from
Apr 4, 2024
Merged

feat: elaborate TODOs #227

merged 4 commits into from
Apr 4, 2024

Conversation

civsiv
Copy link
Contributor

@civsiv civsiv commented Mar 28, 2024

Closes: #225

@@ -417,20 +417,24 @@ public Uri RenderOrderId(OrderType orderType, Guid uuid)
return this.RenderOrderId(new OrderIdComponents { OrderType = orderType, uuid = uuid });
}

//TODO reduce duplication of the strings / logic below
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implemented

Comment on lines 731 to 732
// TODO: add this error class to the library
// CS: Is this still the case? Unclear where this library is, and hard to believe OpenBookingError would not be in the libary
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not fully sure I understand what this is talking about, so ignore me if this is irrelevant, but it looks like OpenBookingError is part of OpenActive.NET (here).

Could this comment be referring to OpenBookingException? And if so, what library..?

Or maybe it means that there should be a special OnlyBookableOpportunitesPermittedInTestInterfaceError class or something, idk

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeh I'm also very confused by the comment. I think OnlyBookableOpportunitesPermittedInTestInterfaceError in OpenActive.Net makes most sense so will amend the comment

Comment on lines 360 to +361
// TODO: The static example below should come from the database (which doesn't currently support tax)
// This is because it can be different for each Seller and needs to calculated at the time of booking
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this cause any bugs at present? If yes then maybe should be a GH issue?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, not yet I think

civsiv and others added 3 commits April 3, 2024 17:45
* feat: remove remainingAttendeeCapacity and maximumAttendeeCapacity from B response

* remove from P response too
@civsiv civsiv merged commit 821e182 into master Apr 4, 2024
19 of 21 checks passed
@civsiv civsiv deleted the feature/elaborate-todos branch April 4, 2024 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TODOs in ref impl
2 participants