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

Move Configuration to separate module #798

Closed

Conversation

rofle100lvl
Copy link
Contributor

I decided to separate Configuration and here is why.
First of all, it's a big piece of logic. And it should be well separated. Also I'm planning to make it start point in public API. So the scheme would be like that:
User -> Setup Configuration -> Launch ProjectDriver to the project -> Got SourceGraph and can analyze anything he wants.

For that purpose Configuration should be separated in different module. Because of that, Its needed to make some moves around (because cycling dependencies)
BaseLogger -> SeparatedModule
Logger, Glob, Shell, SwiftVersion, SwiftParser -> Utils
Configuration -> SeparatedModule

@rofle100lvl
Copy link
Contributor Author

@ileitch What do you think about scheme for public API use?

@rofle100lvl rofle100lvl force-pushed the SeparateConfiguration branch 2 times, most recently from b95995a to e8a599e Compare August 28, 2024 07:30
@rofle100lvl
Copy link
Contributor Author

rofle100lvl commented Aug 28, 2024

@ileitch Can you check it? New and new conflicts will appear. And also I have a talk in october and by this time i really want to move my project from fork to spm dependency...

@ileitch
Copy link
Contributor

ileitch commented Sep 15, 2024

I've implemented this in #817 as I took a slightly different approach, but thanks for the contribution all the same!

@ileitch ileitch closed this Sep 15, 2024
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