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
when several links of a document share the same last path portion, the HAL codec (more precisely the _map_to_coreapi_key function) use the same document key to store them. The consequence is that the document misses them all but the last.
My use case is Slimpay's API where the root document uses links of the form https://api.slimpay.net/alps#<foo> where can take several different values. The key computed for all these links is "alps", and the parser overrides the previously parsed link.
I think the codec should not alter the API writter's choice regarding this key and take it as is, to avoid such caveats. What do you think?
This would obviously change the codec API so care would have to be taken to deprecate the _map_to_coreapi_key function slowly in the 1.x branch and introduce the change in the 2.x series.
Hi there,
when several links of a document share the same last path portion, the HAL codec (more precisely the
_map_to_coreapi_keyfunction) use the same document key to store them. The consequence is that the document misses them all but the last.My use case is Slimpay's API where the root document uses links of the form
https://api.slimpay.net/alps#<foo>where can take several different values. The key computed for all these links is "alps", and the parser overrides the previously parsed link.I think the codec should not alter the API writter's choice regarding this key and take it as is, to avoid such caveats. What do you think?
This would obviously change the codec API so care would have to be taken to deprecate the
_map_to_coreapi_keyfunction slowly in the 1.x branch and introduce the change in the 2.x series.