DEV-16369: Refactor objects-catalog.webc to render ALL objects in /content/
#872
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anderspollack
changed the title
objects-catalog.webc to render ALL objects in /content/objects-catalog.webc to render ALL objects in /content/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This refactor changes the behavior of
layout: objects-page(objects-catalog.webc) to render all objects in project, regardless of wherelayout: objects-pageis located in the/content/directory.We didn't originally implement it this way as we assumed we could have multiple directory-specific
objects-pagelayouts in the same project (which currently does not work - the objects of the first instance of anobjects-pageget displayed in all instances). But this should fix the immediate issue