Skip to content

feat: Expose paths to project configuration files in projectData #3478

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

Merged
merged 1 commit into from
Mar 20, 2018

Conversation

rosen-vladimirov
Copy link
Contributor

Expose new properties in projectData with paths to specific configuration files. This allows all tools that require CLI to get these paths and will not require changes in them when the structure of project is modified.
Introduce additional constants and use them in the code

@rosen-vladimirov rosen-vladimirov added this to the 4.0.0 milestone Mar 20, 2018
@rosen-vladimirov rosen-vladimirov self-assigned this Mar 20, 2018
Copy link
Contributor

@Mitko-Kerezov Mitko-Kerezov left a comment

Choose a reason for hiding this comment

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

LGTM

Expose new properties in `projectData` with paths to specific configuration files. This allows all tools that require CLI to get these paths and will not require changes in them when the structure of project is modified.
Introduce additional constants and use them in the code
@rosen-vladimirov rosen-vladimirov force-pushed the vladimirov/expose-config-files branch from 0a27afa to d8e02ca Compare March 20, 2018 15:04
@rosen-vladimirov rosen-vladimirov merged commit bf3969b into release Mar 20, 2018
@rosen-vladimirov rosen-vladimirov deleted the vladimirov/expose-config-files branch March 20, 2018 16:01
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.

2 participants