Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

fix(elementexplorer): setting the browser root element #3538

Closed
wants to merge 1 commit into from

Conversation

cnishina
Copy link
Member

@cnishina cnishina commented Sep 9, 2016

closes #3465

@cnishina cnishina added this to the 4.1.0 milestone Sep 9, 2016
- provide logging messages to useAllAngular2AppRoots
- provide logging messages to set the root element

closes angular#3465
@cnishina cnishina changed the title fix(elementexplorer): check for an element with all angular 2 app roots fix(elementexplorer): setting the browser root element Sep 10, 2016
@cnishina
Copy link
Member Author

This is CLI driven but there are cases where this issue is not resolved for downstream projects like elementor.

@juliemr
Copy link
Member

juliemr commented Sep 12, 2016

We talked about this offline, and the conclusion for now is:

  • If the user has not specified how to search for angular, have element explorer look on body and then try useAllAngular2AppRoots (a.k.a rootEl = ''). This will let element explorer work without configuration for 90% of apps.
  • Let's rethink the API here, since the question "how do I find Angular on my page" is getting messy and prompting questions from users. It's not obvious that the cryptically named useAllAngular2AppRoots has anything to do with rootEl, and people don't know how to use it.

@cnishina
Copy link
Member Author

Closing in favor of #3570.

@cnishina cnishina closed this Sep 19, 2016
@cnishina cnishina deleted the elementexplorer_ng2 branch November 5, 2018 17:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Could not find testability for element when use elementor or element explorer
3 participants