invalidate _content
on rebuild if necessary
#156
Merged
+31
−0
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.
There's currently a bug in
Entry
where_content
isn't invalidated properly on rebuilds. This can lead to changes being made by a developer that will ultimately never be bundled on a local development server; the only real mitigation in this case is to re-start your server.The failing scenario is as follows:
Entry
we set_content
because some file string's length is less thancontentLimit
contentLimit
content
is subsequently accessed, we'll get the previously cached_content
, not the new updates as you'd expect