[ResourceBundle] Check for existence of controller class before creating definition #1505
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
pjedrzejewski
pushed a commit
that referenced
this pull request
May 14, 2014
[ResourceBundle] Check for existence of controller class before creating definition
|
Sounds good, thank you Craig! |
pamil
pushed a commit
to pamil/Sylius
that referenced
this pull request
May 7, 2019
[ResourceBundle] Check for existence of controller class before creating definition
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.
Not sure if there's a better way to do this or not but I have a couple of entities that don't require controllers and I'm using the Configuration to resolve target entities / change classes etc.