-
Notifications
You must be signed in to change notification settings - Fork 20
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
Versioning CSP Application #29
Comments
In ideal world classes and routines also can be exported as plain text. This can be probably be done in version 2.0 of this plugin that will break compatibility with existing repositories. Not to mention that version 2.0 will highly unlikely ever come. |
Okay, I agree fully, but as that was made today, I'm just having trouble with the versioning of binary files, for example, when I need an image versioning. There is a possibility now change the project so that binary files are versioned in its original format? |
Another alternative would be to indicate the settings the way the CSP application and versioning directly to physical folder, and not export Caché. |
Any news? |
What is the problem with binary files? They are exported in standard $system.OBJ.Export base64-XML format. It has the same problems as export of js in XML-like format. Or cls. |
For CSP applications I do not see the need for versioning export XML files, this because within the application often have files from other formats that would provide greater control if they were versioned for its extension origin.
The text was updated successfully, but these errors were encountered: