A full-featured, open-source content management framework built with Node.js that empowers organizations by combining in-context editing and headless architecture in a full-stack JS environment.
Summarize the changes briefly, including which issue/ticket this resolves. If it closes an existing Github issue, include "Closes #[issue number]"
What are the specific steps to test this change?
N/A, I've reproduced the bug and the fix in the client's repo, it's unclear if it can be done with a simple test configuration but the issue was obvious
What kind of change does this PR introduce?
(Check at least one)
[X] Bug fix
[ ] New feature
[ ] Refactor
[ ] Documentation
[ ] Build-related changes
[ ] Other
Make sure the PR fulfills these requirements:
[X] It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
[X] The changelog is updated
[ ] Related documentation has been updated
[ ] Related tests have been updated
If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.
Summary
Summarize the changes briefly, including which issue/ticket this resolves. If it closes an existing Github issue, include "Closes #[issue number]"
What are the specific steps to test this change?
N/A, I've reproduced the bug and the fix in the client's repo, it's unclear if it can be done with a simple test configuration but the issue was obvious
What kind of change does this PR introduce?
(Check at least one)
Make sure the PR fulfills these requirements:
If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.
Other information: