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.

Sign up for GitHub

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

Jump to bottom

Analyze and manipulate StringTemplate files #165

Open
khatchad opened this issue Jul 11, 2016 · 0 comments
Open

Analyze and manipulate StringTemplate files #165

khatchad opened this issue Jul 11, 2016 · 0 comments
Labels
feature
Milestone
Future Transforma...

Comments

@khatchad
Copy link
Member

It seems that some projects (see #164 and eclipse-collections/eclipse-collections#128) use template files to generate abstract skeletal implementers for a particular interface. This seems to be particularly useful for generating skeletal implementation classes that deal with all the primitive types.

Currently, the tool does not analyze or manipulate such template files. It would be particularly useful to identify source code files generated from templates and, instead of manipulating the derived source code, manipulating the corresponding template mechanism.
@khatchad khatchad added this to the Future Transformation milestone Jul 11, 2016
khatchad pushed a commit to ponder-lab/eclipse-collections that referenced this issue Jul 12, 2016
Removed skeletal implementations from template file.
95dc8cd 
These implementations were automatically copied to PrimitiveIterable. This step represents the corresponding removable. This is a manual step and a workaround of ponder-lab/Migrate-Skeletal-Implementation-to-Interface-Refactoring#165.

Signed-off-by: Raffi Khatchadourian <[email protected]>
itohro pushed a commit to eclipse-collections/eclipse-collections that referenced this issue Jul 13, 2016
@itohro
Apply skeletal implementation to interface migration automated refact…
6a4e99a 
…oring.

* Applied skeletal implementation to interface migration automated refactoring.

Signed-off-by: Raffi Khatchadourian <[email protected]>

* Unmigrate methods that crossed module boundaries.

Signed-off-by: Raffi Khatchadourian <[email protected]>

* Convert tab characters to spaces.

Signed-off-by: Raffi Khatchadourian <[email protected]>

* Remove unused import straggler.

Signed-off-by: Raffi Khatchadourian <[email protected]>

* Move curly brace to newline to conform to destination interface coding styles.

There are differences in coding styles between the source module, where the implementations originated, and the destination module, where the default methods were created. This commit is to conform to to new coding style. This is a manual step as we do not currently analyze the difference in coding styles between projects/modules.

Signed-off-by: Raffi Khatchadourian <[email protected]>

* Removed skeletal implementations from template file.

These implementations were automatically copied to PrimitiveIterable. This step represents the corresponding removable. This is a manual step and a workaround of ponder-lab/Migrate-Skeletal-Implementation-to-Interface-Refactoring#165.

Signed-off-by: Raffi Khatchadourian <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
Future Transformation
Development

No branches or pull requests
1 participant
@khatchad