Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
parser: support remote dependencies #930
Conversation
|
The approach looks good to me. Thanks for working on this. Please fix the complexity issue and check that the coverage for the files you've modified hasn't decreased and that all new code is covered. Coverage can be a bit wonky at times. :) |
I'm not sure how to deal with that, should I just split the function? :o
This is due to the exception that I protect from in the for-cycle over pending_validation_entries. |
|
I think you can split out the post processing for the pending entries into its own method. You can probably trigger that exception by referencing a pending part that has a missing 'parts' in the yaml. I think we want to keep the |
|
Nice job killing two birds with one stone. :-) +1 |
3v1n0
added some commits
Nov 24, 2016
sergiusens
changed the title from
Parser support remote dependencies
to
parser: support remote dependencies
Nov 30, 2016
sergiusens
approved these changes
Dec 1, 2016
Thanks for this, I have a feeling this would be easier to follow if we make it less procedural and more OO. What do you think?
If @josepht approved I am fine with it though
|
@sergiusens completely agree... And in fact so it was "almost" stating my initial comment on PR first post, but things were already so much procedural, so I didn't want to rewrite everything. |
3v1n0 commentedNov 28, 2016
Ensure that we re-parse the parts that have missing dependencies after we've added all the valid ones to the
master_parts_listI would have fixed this in a cleaner way (allowing to include parts of a snapcraft.yaml that are good, and ignoring the bad ones only) but it would have caused a major refactor of the parser which probably is better to avoid.
Fixes LP: #1645350
@josepht, please have a look to this.