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
I had always assumed that links in embedded resources would be documented as part of the embedded resource's documentation, rather than in the embedding resource's documentation. That may not be an assumption that suits everyone. If you don't want to take this approach then the options currently available are:
Use a custom link extractor and produce a single snippet but this means that you can't assert that the links were in the right place in the payload
Use a custom snippet, probably a LinksSnippet subclass, and produce two separate snippets with different names.
The text was updated successfully, but these errors were encountered:
Inspired by this question on Stack Overflow from @matsev.
I had always assumed that links in embedded resources would be documented as part of the embedded resource's documentation, rather than in the embedding resource's documentation. That may not be an assumption that suits everyone. If you don't want to take this approach then the options currently available are:
LinksSnippet
subclass, and produce two separate snippets with different names.The text was updated successfully, but these errors were encountered: