You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
馃敭 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, butimporter 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 forimporter update
.The text was updated successfully, but these errors were encountered: