Replies: 3 comments 8 replies
-
|
I think I'm leaning towards option 1, because all other options have clear downsides:
If we show just a warning for long enough (1 year+), eventually removing support for mkdocs.yml will not be seen as so outrageous. |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
@oprypin can ppl disable warnign for mkdoc.yml? y must we need new filename when all is same? |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Something possibly needs to be done regarding which file is used for configuration. There are a lot of possible options - at least four:
Support
properdocs.yml, fall back tomkdocs.ymland show a warning ifmkdocs.ymlis used.Support
properdocs.yml, fall back tomkdocs.yml, but fail if both files exist.Support only
mkdocs.yml.Support only
properdocs.yml.Currently (3) is active.
However we should seek to make an active decision regarding this, because introducing a breaking change later will be more painful.
It's less painful to ask users to switch to "properdocs.yml" immediately while they're switching everything, but on the other hand it's also very attractive to just not ask them to change the file in any way at all.
Beta Was this translation helpful? Give feedback.
All reactions