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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option/strategy to define package name when exporting #125

Open
eMaringolo opened this issue Dec 2, 2022 · 0 comments
Open

Add option/strategy to define package name when exporting #125

eMaringolo opened this issue Dec 2, 2022 · 0 comments
Assignees
Labels
exporting Issues related with exporting in Tonel format ux User Experience

Comments

@eMaringolo
Copy link
Collaborator

When exporting an application to files we look for the _TONEL_packageName method and use what it returns if it exists or use the application name as the package name.

When dealing with "VAST only" situations, such package name is redundant, and it is often more convenient to only use the app name, without discarding such _TONEL_packageName selector (for future updates coming from an upstream repository).

We need to add an option or a strategy to the TonelWriter to ignore such method and use the app name, such option would be default and included in the #beVASTOnly convenience setup.

@eMaringolo eMaringolo added ux User Experience exporting Issues related with exporting in Tonel format labels Dec 2, 2022
@eMaringolo eMaringolo self-assigned this Dec 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exporting Issues related with exporting in Tonel format ux User Experience
Projects
None yet
Development

No branches or pull requests

1 participant