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

[5.8] Rename cached schema to cached scheme #26706

Conversation

TBlindaruk
Copy link
Contributor

Rename cachedSchema to cachedScheme , since cachedSchema is deprecated from
#26640

P/S: please merge 5.7 br into master before merge this PR

gabfr and others added 30 commits November 1, 2018 16:03
…outes to the separate method; (laravel#26616)

- moved registration of the typical reset password routes to the separate method, like it is for `emailVerification` routes;
Both methods internally use the `parseIds` method which, unless extended by a model, handles a `Model`.  Since these methods list out all of the supported argument types, list this alternative as well.
This clarifies that connection will be set for any retrieved relation without a custom connection name.

See https://github.com/laravel/framework/issues/24944#issuecomment-439912177
I removed the container namings in the Fluent and MessageBag classes because they don't make sense here. I think these are leftovers from a previous refactor.

I also made sure that the other namings are consistent in these classes.
# Conflicts:
#	src/Illuminate/Foundation/Application.php
…UrlGenerator`

 - rename `$cachedSchema` property to `$cachedScheme` in `Routing\UrlGenerator`,
 since in laravel#26640 PR property is deprecated;
@taylorotwell
Copy link
Member

Looks like there is a lot of other commits in this PR. Can you send again?

@TBlindaruk
Copy link
Contributor Author

@taylorotwell ,

It is happening since of 5.7 br is not in the master ;)

Could you merge 5.7 into master, please?

@driesvints
Copy link
Member

@TBlindaruk if you want to add something to the next release (5.8) you can simply branch of the master branch. This will prevent commits from 5.7 to also be included.

@TBlindaruk
Copy link
Contributor Author

@driesvints , I know this.

But in this PR I have delete of some code which was added only to the 5.7 and not merged to the master yet.

@driesvints
Copy link
Member

@TBlindaruk ah okay! I see @GrahamCampbell just merged 5.7 into 5.8 so you should be able to resend it now :)

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.