Update database template YAML to conform to spec #400
Merged
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
* Back to development * Add Timestamps() macro when generating fizz migrations (gobuffalo#365) * Azure pipelines (gobuffalo#367) * WIP Azure pipelines * Fix typo * Fix soda install script * Fix binary name * Fix tsoda call * Build soda without modules * Use Bash to install soda * Fix pipeline * Fix soda build * Remove go module builds * Fix soda install * Install soda with go install * Fix config parse test * Do not create Docker default DBs * Remove Travis * Update badge in Readme * Remove legacy Anko format fixer (gobuffalo#366) It can still be called using soda fix command. * removes errors.WithStack as its noisy and makes it harder to understand (gobuffalo#372) * removes errors.WithStack as its noisy and makes it harder to understand * fix packr file * Add a fix for old fizz without Timestamps() (gobuffalo#373) * WIP fix old auto-timestamp * Use plush AST to rewrite fizz files * Fix case when files are already using t.Timestamps() * Fix Windows line breaks issue * Add a mention in godocs about the behavior on slices for executors (gobuffalo#375) Fixes gobuffalo#363. * Fix "has_one" pointer association (gobuffalo#378) * hasOneAssociation did not work with pointers * Bump version * Fix IdlePool option (gobuffalo#380) The zero value was not the same as in the stdlib and could cause perfs issues. This will now not call SetMaxIdleConns when IdlePool is set to the zero value. Fixes gobuffalo#376
This commit updates the four database template files to begin using three hyphens, which per the YAML specification is used to signal the start of a document. While not invalid to not include this, as most of the tools don't require this to properly function, by making this change ensures that directives are properly parsed in all parsers. ``` 3.2.3.4. Directives Each document may be associated with a set of directives. A directive has a name and an optional sequence of parameters. Directives are instructions to the YAML processor, and like all other presentation details are not reflected in the YAML serialization tree or representation graph. This version of YAML defines a two directives, “YAML” and “TAG”. All other directives are reserved for future versions of YAML. ```
|
Thanks for you contribution! Can you change your PR to point to the development branch, as asked in the contribution guide? Thanks. |
|
Base branch changed to development using https://help.github.com/en/articles/changing-the-base-branch-of-a-pull-request |
stanislas-m
approved these changes
Jun 20, 2019
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.
This commit updates the four database template files to begin using
three hyphens, which per the YAML specification is used to signal the
start of a document.
While not invalid to not include this, as most of the tools don't
require this to properly function, by making this change ensures that
directives are properly parsed in all parsers per the specification and
ensures that users who leverage linters within their editors and CI pipelines
will not have errors thrown with new projects.