Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silex provider #16

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

mtotheikle
Copy link

This pull requests allows integration to the guzzle data collector with Silex. Documentation on usage is slim right now and no tests have been done.

One thing that still needs to be done and needs discussion is how to load the font files that are needed since we can not use the "asset" filter.

…n is required by http-kernel and config/dependency-injection is not needed if only using bundle in silex context
- Move JS files that need to be loaded into resources so we can include them in the template. This is required for silex
- Add silex service provider

Still need to figure out a way to load the font files that are needed when outside of the Symfony bundle structure.
@ghost ghost assigned ludofleury Nov 8, 2013
@ludofleury
Copy link
Owner

I'm reviewing this asap, thanks a lot.

@mtotheikle
Copy link
Author

Sounds good. Let me know your thoughts on loading of the fonts since we have to handle it a little differently with Silex based applications. It will probably require some configuration I'm thinking.

@ludofleury
Copy link
Owner

Actually I never used the web profiler from Symfony on Silex. I have to try
first. But i guess i understand the prob the "bundle trivial feature"
aren't provided by Silex, so the embedded assets aren't "magically" dumped
right ?
On Nov 15, 2013 12:54 AM, "Michael Williams" [email protected]
wrote:

Sounds good. Let me know your thoughts on loading of the fonts since we
have to handle it a little differently with Silex based applications. It
will probably require some configuration I'm thinking.


Reply to this email directly or view it on GitHubhttps://github.com//pull/16#issuecomment-28535535
.

@mtotheikle
Copy link
Author

Correct. This means that we don't know where these assets will live on the web server

@ludofleury
Copy link
Owner

Hey, so my question is: is this a common practice to include silex provider in a bundle ? I have a solution which is actually provide a post composer script to dump the assets in a configured path... But it would be extra hackish and since there is no hard convention in silex, it would require an user input.

The other solution is to actually separate this provider in another repo with a composer dependecy to this bundle. Then we could add a script/command to dump the assets.

@mtotheikle
Copy link
Author

I'm not sure what the best practice is. As long as the other repo is referenced within this one so that developers easily see it exist I'm sure it would be fine to live on it's own.

@ludofleury
Copy link
Owner

Ok, let's do this. I'll reference it in the readme 👍

@ludofleury
Copy link
Owner

Be aware that this bundle could be merged into this one: misd-service-development/guzzle-bundle#29

@mtotheikle
Copy link
Author

Great to see the merging of the bundles happening!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants