-
-
Notifications
You must be signed in to change notification settings - Fork 977
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
Various missing information #1570
Comments
See #1211 -- 4.3 "annual_reports" feature is on the list of undocumented things |
How are clients supposed to guard against these undocumented APIs when they are received in the JSON response? |
At the very least for the notifications API, several clients show a "notification of unknown type" item in their notification UIs. I would say that the notification handler could be thought of as a case-based structure:
|
Right but what about the content of the notification? As far as I have inspected, it doesn't provide a status to indicate what the notification actually is. It returns an account but there is no context provided. How do I inform the user that this notification is an annual report notification that they can view their report even if I were to display it as an unmarked notification? |
You can generally expect a This could be rendered as a single line of text that says: "Unknown notification received: {type}" If you're talking about how to handle notifications of type |
The documentation is missing some information.
Entity
Notification
,type
attribute is missingannual_report
string as part of its enumeration. I received a special annual report notification. It broke my client.Likewise
AnnualReport
entity exists but the documentation does not list it.As far as I was able to gather, it includes
year
attribute and an optionalaccount
attribute.Also, entity
NotificationGroup
needs to include an optionalannual_report
attribute which I believe is anAnnualReport
type.The text was updated successfully, but these errors were encountered: