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

Support configuring package resolution in FE #31549

Open
sigmundch opened this Issue Dec 5, 2017 · 3 comments

Comments

3 participants
@sigmundch
Member

sigmundch commented Dec 5, 2017

In build systems like bazel, the analysis server used within the IDE needs to customize package resolution rules. This customization cannot be done by creating a .packages file because we cannot list all the possible packages that the user may need.

Analyzer in the past achieved this by creating custom package-uri translation rules. I believe we could achieve a similar result by letting clients of the FE specify a Packages object as an option (instead of just a .packages file).

@keertip keertip added this to the 2.0-alpha milestone Dec 6, 2017

@kmillikin kmillikin added this to Incoming in Dart Front End Jan 3, 2018

@dgrove

This comment has been minimized.

Show comment
Hide comment
@dgrove

dgrove Feb 23, 2018

Member

@sigmundch were there any updates to this?

Member

dgrove commented Feb 23, 2018

@sigmundch were there any updates to this?

@sigmundch

This comment has been minimized.

Show comment
Hide comment
@sigmundch

sigmundch Feb 23, 2018

Member

No - however, I don't believe this is needed for 2.0 at this time.

It is needed for integrating analysis server with the FE in an IDE in bazel, which is a goal a bit further down. I've updated the milestone.

Member

sigmundch commented Feb 23, 2018

No - however, I don't believe this is needed for 2.0 at this time.

It is needed for integrating analysis server with the FE in an IDE in bazel, which is a goal a bit further down. I've updated the milestone.

@sigmundch sigmundch modified the milestones: 2.0-alpha1, 2.0 Feb 23, 2018

@dgrove

This comment has been minimized.

Show comment
Hide comment
@dgrove

dgrove Mar 18, 2018

Member

Because the Analyzer FE won't be replaced by CFE in Q2, removing from the 2.0 milestone.

Member

dgrove commented Mar 18, 2018

Because the Analyzer FE won't be replaced by CFE in Q2, removing from the 2.0 milestone.

@dgrove dgrove removed this from the 2.0 milestone Mar 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment