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
It can be nice to have default Trailpack family, and have a category "default" with Trailpacks retrieve from npm.
Or retrieve all Trailpacks from npm and parse keywords (or put a trailpackCategory field under package.json for trailpack) and show them directly on the right category.
Example :
I make a new web server trailpack, I just have to add trailpackCategory : 'webserver' and it will automatically appear on "Web server" category on TrailsMix.
That can be cool :)
The text was updated successfully, but these errors were encountered:
Definitely a cool idea, and I think having these Trailpacks "pre-categorized" will go a long way towards getting a solid mental model of the Trails ecosystem beyond their effectiveness in automating the UI.
We are already diagnosing branding for each "type" of Trailpack, so having each Trailpack type made explicit through its configuration will be very useful as a reference.
It can be nice to have default Trailpack family, and have a category "default" with Trailpacks retrieve from npm.
Or retrieve all Trailpacks from npm and parse keywords (or put a trailpackCategory field under package.json for trailpack) and show them directly on the right category.
Example :
I make a new web server trailpack, I just have to add
trailpackCategory : 'webserver'
and it will automatically appear on "Web server" category on TrailsMix.That can be cool :)
The text was updated successfully, but these errors were encountered: