You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, if you pass xclogparser the --project option and give it an incorrect project name, LogFinder throws an error
Error. There is no directory for the project \(name) in the DerivedData
folder in \(derivedDataDir.path). Please specify the path to the xcactivitylog
with --file or the right DerivedData folder with --derived_data
Would it be possible to include in the message the nearest matching/all projects available in the DerivedData directory? I would find this helpful if, for example, I incorrectly enter a --project name and don't easily have the ability to inspect the DerivedData directory.
Happy to submit a PR if so, just curious if that's intentionally been omitted and if this would be welcomed. Also - love the project - and thanks for publishing it!
The text was updated successfully, but these errors were encountered:
I think the reason we don't do this is because the derived data directory could also be often customized, so we would we have no idea where exactly it could be and where we to look for similar directories. I'll ask @ecamacho for a second opinion on this.
Hi!
Right now, if you pass
xclogparser
the--project
option and give it an incorrect project name,LogFinder
throws an errorWould it be possible to include in the message the nearest matching/all projects available in the DerivedData directory? I would find this helpful if, for example, I incorrectly enter a
--project
name and don't easily have the ability to inspect the DerivedData directory.Happy to submit a PR if so, just curious if that's intentionally been omitted and if this would be welcomed. Also - love the project - and thanks for publishing it!
The text was updated successfully, but these errors were encountered: