When serializing nodes for links, only include small subset of data #944
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, if an AppLink was rendered from a node, the entire node was serialized. Since a node is a non-trivially large JSON structure, this resulted in a lot of wasted serialization, as only a few pieces of information are necessary to generate a link. As a result, pages that rendered a non-trival amount of links (in this case, SectionHierarchy) would be very laggy as the browser struggled to do all that serialization.
This commit filters only those properties necessary to render a link:
id
,category
,name
, andin_taxon_label
.(Note that this stretegy is already used in AssociationSummary.vue).
Fixes #912