You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Articles endpoint SDK support
* Collections Endpoint Support (#523)
* Sections Endpoint Support (#524)
* Added Collections endpoint SDK support
* Added test coverage
* Added dirty_tracking support for nested objects (#525)
* Added support to check for equality of two resources (#527)
* Updated README and logged changes for v4.1.0 (#526)
If you are building a third party application you can get your access_tokens by [setting-up-oauth](https://developers.intercom.io/page/setting-up-oauth) for Intercom.
section.translated_content.es = {name:"Sección en español"}
622
+
intercom.collections.save(section)
623
+
624
+
# Delete an section
625
+
intercom.sections.delete(section)
626
+
```
627
+
528
628
### Errors
529
629
530
630
There are different styles for error handling - some people prefer exceptions; some prefer nil and check; some prefer error objects/codes. Balancing these preferences alongside our wish to provide an idiomatic gem has brought us to use the current mechanism of throwing specific exceptions. Our approach in the client is to propagate errors and signal our failure loudly so that erroneous data does not get propagated through our customers' systems - in other words, if you see a `Intercom::ServiceUnavailableError` you know where the problem is.
0 commit comments