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

Client-side service to track client state #1830

Closed
dkulieshov opened this issue Jul 18, 2016 · 2 comments
Closed

Client-side service to track client state #1830

dkulieshov opened this issue Jul 18, 2016 · 2 comments
Assignees
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Milestone

Comments

@dkulieshov
Copy link

dkulieshov commented Jul 18, 2016

Overview

In general it would be very useful if we could automatically track changes of client state in real time along with simple mechanism to add event handlers and transparent data format to represent those events in one place and in one manner.

Description

There is a number of possible implementations, my suggestion is to provide a service that will track registered changes of IDE state:

  • open/close file in an editor
  • expand/collapse directory in a project tree
  • etc.

Events are tracked irrespective of their origins but only those that are registered along with their handlers. Those events are processed by the service and probably transformed into internal representation comfortable for serialization and transportation. I'm currently looking towards Json as it simplifies data transfer overJson RPC protocol.

Finally, there are a few important points I would like to draw your attention to:

  • We should definitely think on comfortable and generalized we of defining and providing of all valuable state related data.
  • Another important thing is to provide a convenient and extendable way to serialize and/or transfer those events further
  • It is quite obvious that we will need to track more state-related events in future, so we should also keep that in mind and think on how we can easily track new event type and represent its data further.
@dkulieshov dkulieshov added kind/enhancement A feature request - must adhere to the feature request template. sprint/next team/ide labels Jul 18, 2016
@dkulieshov dkulieshov self-assigned this Jul 18, 2016
@vparfonov vparfonov added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. sprint/current and removed sprint/next labels Jul 20, 2016
@dkulieshov dkulieshov added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Aug 2, 2016
@dkulieshov dkulieshov removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Sep 18, 2016
@dkulieshov dkulieshov added this to the 5.0.0-M1 milestone Sep 18, 2016
@TylerJewell
Copy link

@dkuleshov - can you cross link the PR for this please? Thanks.

@dkulieshov
Copy link
Author

This issue was resolved under #2339

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Projects
None yet
Development

No branches or pull requests

3 participants