Specify which railties we want to require #60
Merged
Conversation
This file contains 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
We are being explicit about which railties we want to require in our application. This for be able to deploy our application succesfully.
We have noticed how the body of the posts is not being rendered correctly. I have found that the `find_and_preserve` method is the one causing the issue. If we move it, the body of the posts will be rendered correctly.
Ilyeo
force-pushed
the
chore/specify-which-railties-we-want-to-require
branch
from
72038e7
to
f8f4748
Compare
Ilyeo
force-pushed
the
chore/specify-which-railties-we-want-to-require
branch
from
9c86ac7
to
d23c935
Compare
The extension of the asset is required; otherwise, it won't be present in the asset pipeline.
Ilyeo
force-pushed
the
chore/specify-which-railties-we-want-to-require
branch
from
d23c935
to
2eb5902
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Quick Info
We are being explicit about which railties we want to require in our
application. This is to be able to deploy our application successfully.
Also, we fixed an issue in the body of the posts when rendered and
addressed a deprecation warning about some assets not being
present in the asset pipeline. The latter occurs during builds.