Comments (3)
I dont understand what "changed feature contexts" mean in this context. Also, feature contexts should not be visible when synchronising because at that point, no feature contexts exist.
from variantsync.
The term feature context was more broadly used here. The idea was that only contexts are shown that have associated and not-yet-synchronized changes. Why should users care about contexts for which no changes exist at this point.
In the old implementation, the feature context was the same as the mapping. An open question is whether we want to show feature contexts in this view or mappings or even both. Filtering by means of mappings could mean that we miss relevant edits during synchronization. For example when replacing a line, the removal would have a different mapping than the added line. Synchronizing changes aligned with mappings could lead to more inconsistencies as when using contexts. Also, it feels that context are a higher abstraction at this point.
from variantsync.
Thanks for clarification. Good questions that I would like to investigate next month. Currently, the idea was to synchronise edit-based and edits are bound to a feature context. So this is in line with your suggestion.
from variantsync.
Related Issues (20)
- Data Structure for Abstract Syntax Trees
- Importing and Exporting AST to and from JSON
- Simple Parser for Text File Lines
- Abstract and Extract Existing Feature Trace Infrastructure
- Implement Line-Based Feature Traces with ASTs (After Issue #54)
- Code Style: Magic Numbers and Strings
- Documentation: Document old Code
- JsonParserTest
- FeatureIDE-Wrapper Plugin
- Eclipse-GUI-Plugin
- Feature Drop Down menu empty
- CI: Use Project Settings Warning
- Enhance AST with Feature Mappings HOT 1
- AST: Add Propositional Logic to Abstract Syntax Tree HOT 1
- Refactoring of Feature Context
- broken build HOT 1
- Legacy Bug: Eclipse Highlighter do incorrectly move with changed lines
- Legacy Bug: AMarkerInformation needs to be updated continuously
- AMarkerInformation to Eclipse Markers
- Could not serialize prop4j.node to json
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from variantsync.