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

Chrome debugger integration #252

Conversation

AObuchow
Copy link
Contributor

Fix #230

@AObuchow AObuchow force-pushed the Chrome_debugger-integration branch 3 times, most recently from ba6a6d6 to 1add0b5 Compare September 11, 2019 14:06
Start packaging chrome debugger

Signed-off-by: Andrew Obuchowicz <aobuchow@redhat.com>
Start refactorization of node/firefox/chrome debug adapter logic

Signed-off-by: Andrew Obuchowicz <aobuchow@redhat.com>
Refactorings for debugTab's and variables used in DebugDelegates

Signed-off-by: Andrew Obuchowicz <aobuchow@redhat.com>
Refactorings for debugTab's and DebugDelegates

Signed-off-by: Andrew Obuchowicz <aobuchow@redhat.com>
@@ -4,7 +4,8 @@ bin.includes = META-INF/,\
.,\
plugin.xml,\
language-servers/package-lock.json,\
language-servers/node_modules/,\
language-servers/chrome-debug-adapter/extension/node_modules/,\
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't have to do that if we can have the module treated as regular npm in node_modules.

</arguments>
<workingDirectory>language-servers/</workingDirectory>
</configuration>
</execution>
</executions>
</plugin>

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for those extra lines.

@@ -0,0 +1,87 @@
--- org.eclipse.wildwebdeveloper/src/org/eclipse/wildwebdeveloper/InitializeLaunchConfigurations.java
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like some garbage file

@mickaelistria
Copy link
Contributor

Can we close it as it seems like #256 replaces it?

@AObuchow AObuchow closed this Sep 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Integrate Chrome debugger
2 participants