Standardize output for installs #17

Activity

1. RamblingCookieMonster commented on Jan 15, 2018

   

   RamblingCookieMonster

   on Jan 15, 2018

   Last edited by RamblingCookieMonster

   CollaboratorAuthor

   More actions

   Some quick thoughts, current state is quite ugly with some types killing output, other types giving way too much output, etc.

   • Include all Dependency metadata
   • Include a Status boolean, depending on whether the install was a success (as much as we can tell)
   • Include a StatusDetail (not tied to the name) string, which expands on Status:
     • If we failed, try to include a friendly description of why it failed and potentially how to fix - otherwise, text of whatever unexpected error we caught.
     • If we succeeded, indicate how - e.g. dependency already existed, or we used whatever method the dependency script called for
   • Include a Output string, including output from whatever tool the script calls (in case the user
   • Maybe include a property for each stream (Output, Error, Warning)? Always handy to have raw data from these streams, as well as some distilled bit (StatusDetail)
   • Use format data to limit to something like Dependency Name, Dependency Type, Status, StatusDetail, letting folks explore as needed

   Anything else? Is this too much?

   Cheers!
2. github-actions commented on May 18, 2026

   

   github-actionsBot

   on May 18, 2026 – with GitHub Actions

   More actions

   This issue has had no activity for 60 days. It will be closed in 30 days unless there is new activity or a maintainer removes the stale label.
3. github-actions

   added

   status: staleNo activity, candidate for closingNo activity, candidate for closing

   on May 18, 2026
4. HeyItsGilbert

   added this to PSDepend Revivalon May 19, 2026
5. github-project-automation

   moved this to Todo in PSDepend Revivalon May 19, 2026
6. HeyItsGilbert

   added this to the v0.5.0 - Stabilization milestone on May 19, 2026
7. github-actions

   removed

   status: staleNo activity, candidate for closingNo activity, candidate for closing

   on May 21, 2026
8. github-actions commented on Jul 21, 2026

   

   github-actionsBot

   on Jul 21, 2026 – with GitHub Actions

   More actions

   This issue has had no activity for 60 days. It will be closed in 30 days unless there is new activity or a maintainer removes the stale label.
9. github-actions

   added

   status: staleNo activity, candidate for closingNo activity, candidate for closing

   on Jul 21, 2026
10. github-actions commented on Aug 21, 2026

    

    github-actionsBot

    on Aug 21, 2026 – with GitHub Actions

    More actions

    Closing due to inactivity. Please re-open if this is still relevant against the current version.
11. github-actions

    closed this as not plannedon Aug 21, 2026
12. github-project-automation

    moved this from Todo to Done in PSDepend Revivalon Aug 21, 2026