Skip to content

Allow a custom config class to be used via class_alias - #112

Merged
duellsy merged 1 commit into
VentureCraft:developfrom
Limelyte:develop
Nov 7, 2014
Merged

duellsy merged 1 commit into
VentureCraft:developfrom
Limelyte:develop

Conversation

@ivelrrat

@ivelrrat ivelrrat commented Nov 7, 2014

Copy link
Copy Markdown
Contributor

From develop this time.

duellsy added a commit that referenced this pull request Nov 7, 2014
Allow a custom config class to be used via class_alias
@duellsy
duellsy merged commit 9b40897 into VentureCraft:develop Nov 7, 2014
@GrahamCampbell

Copy link
Copy Markdown
Contributor

This is a bad practice, and should not be done. The best thing to do here would be to resolve the config repository out of the ioc.

@duellsy

duellsy commented Nov 7, 2014

Copy link
Copy Markdown
Member

I can't see this causing any issues however if you'd like to submit an alternative PR I'd be open to it

@GrahamCampbell

Copy link
Copy Markdown
Contributor

It would 100% cause issues for people who have deleted all the facades aliases.

@duellsy

duellsy commented Nov 7, 2014

Copy link
Copy Markdown
Member

Granted

@GrahamCampbell

Copy link
Copy Markdown
Contributor

I'll send a pull...

@duellsy

duellsy commented Nov 7, 2014

Copy link
Copy Markdown
Member

Cheers

@GrahamCampbell

Copy link
Copy Markdown
Contributor

Actually, when are you doing a laravel 5 only version, because it would make a load of sense to use the config repository contract?

@GrahamCampbell

Copy link
Copy Markdown
Contributor

#113 Should work on laravel 4 and laravel 5.

duellsy pushed a commit that referenced this pull request Mar 3, 2021
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.

3 participants