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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Add auto-generated notice at the top of generated file #15

Closed
rytswd opened this issue Jul 16, 2021 · 2 comments 路 Fixed by #55
Closed

[Feature Request]: Add auto-generated notice at the top of generated file #15

rytswd opened this issue Jul 16, 2021 · 2 comments 路 Fixed by #55
Labels
enhancement New feature or request

Comments

@rytswd
Copy link
Member

rytswd commented Jul 16, 2021

馃敭 Relevant Command

importer generate

馃梻 Language Type

All

馃攷 Request Details

Because Importer is essentially code-generation tool, it should add a note at the top of the file that the file is created by some automation.

This could be useful for importer update as well, but importer update does not have any external template to be reviewed. From code review perspective, importer generate can benefit from this approach, but it may be better not to add such a note for importer update.

@rytswd
Copy link
Member Author

rytswd commented Sep 3, 2021

@rytswd
Copy link
Member Author

rytswd commented Sep 28, 2021

This ticket should be still tackled, as importer generate template.md -o ./some/directory/output.md would break the importer references as the relative paths change. Along with #11, it would be important how the file was created using which template file.

Fixing up relevant paths for each entry may be another possibility, if generate is used once to create a new file, but update to be used going forward. I don't particularly see a use case for that, so that will be considered separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant