kptdev
Support `Kptfile` with `yaml` extension
Not having a yaml extension causes frictions as editors and IDE do not auto-detect the file format of Kptfile. The original reason for not having the extension are not compelling. If we don't do this before 1.0, then we need to suppport Kptfiles with and without extension.
Thanks for the pointer, but that still requires end-users to install plugins/extensions in their editors, no? This issue is about reducing friction by using the simplest mechanism available to deduce file format (the file extension) which doesn't require any additional user action.
no, no it does not.
On Monday, May 3, 2021, Frank Farzan @.***> wrote:
Thanks for the pointer, but that still requires end-users to install plugins/extensions in their editors, no? This issue is about reducing friction by using the simplest mechanism available to deduce file format (the file extension) which doesn't require any additional user action.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/GoogleContainerTools/kpt/issues/1866#issuecomment-831599900, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALR7G7LESBQVOTSDBVIYTTTL4XM7ANCNFSM435LPGMA .
I am not sure this is an M2 task. I think we can even support optional .yaml extension past v1
