Repository navigation
Name the env prefix when install refuses over a foreign table - #29
Merged
Merged
Conversation
Reported by the first consumer install (brandgulp): install refuses before publishing the config, so the old message pointed at keys in a file that did not exist yet. The installation guide now lists sync-definitions after migrate.
This file contains hidden or 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
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.
Summary
From the first consumer install (brandgulp/brandgulp.com#10, doctor 9/9):
settingstable). The message pointed atlaranail.settings.tables.prefix, a key in a file not yet published. It now namesLARANAIL_SETTINGS_TABLE_PREFIX(no file needed) and the publish command for renaming single tables. Refusing before publishing is unchanged.tablesarray (Laravel'smergeConfigFromis a one-levelarray_merge, checked in the framework source);sync-definitionslisted aftermigrate, with why install says "Definitions were not synced" on a fresh app.Not changed: the published migration follows the package's Pint config, not Laravel's stock preset; an app that lints migrations can run its own Pint on it.
Local: 748 tests, Pint clean.