Community
Participate
Working Groups
3.0 RC1 Current the caller of fetchDeferredChildren() always returns an OK status meaning that fetching the children has been successful. There are cases when exceptions will occur and the errors must be reported by the caller. The method should be changed to throw an exception. I don't think this change will break implementers.
This would be an API change nonetheless as it is changing what can be returned. Deferring.
Reopening now that 3.0 has shipped
I have changed it so that we can also return a CANCEL status. Talking to Michael the greater issues seems to be a good way of logging errors. It is possible to implement your own IElementCollector currently to do this but this will likely be something that is worth us providing generally (perhaps with a subtype of IElementCollector we add later). I am going to mark this down in priority now as it is a feature request for us to provide something - we can discuss it further at a more convenient time for the Team team.
Created attachment 14121 [details] Patch that extends IElementCollector with IErrorCollector Here's a patch that extends IElementCollector with an interface that supports error collection. It's pretty straight forward. The only undesirable I can see is the use of instance of on the collector but I don't see a way around that without breaking (or duplicating) API. Also, in the end, IElementCollector2 may be a better name (than IErrorCollector) for the new interface since it follows an already existing convenstion for this type of API extension.
There are currently no plans to work on this feature. Please reopen if you wish to continue on it
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
