Jaremy Creechley

Those last once just make the themes and push them into a Table for quick O(1) lookup/matching. Here's where the matches are found and then used on a node: https://github.com/elcritch/fidgetty/blob/f021659f18550632ddd678fb4bfaf5142769928e/src/fidgetty/fidget_dev/theming.nim#L70

@Araq fixed this PR. I started tracking down another set of issues and got a broken commit mixed in here.

> `Option[string]` is actually worse than `string` if `s.len == 0` is already an errornous state. You added yet another error state on top of the one we already have....

> that every single project/dependency can be in a custom directory and atlas.workspace remembers I'll keep it in mind. Though hopefully these wouldn't be mixed. > Likewise instead of thinking...

> I don't understand it. What is a "parent" workspace? These cannot be nested currently. Why couldn't a workspace be nested? Atlas should find the closest workspace and just use...

> > Looking at the atlas.workspace file deps is not populated > > At least for why it's missing in the first place is likely an oversight writing the default...

Overloading from the URL is bit tricky in general as outside of known sites like github or gitlab it can be difficult to determine if it's git vs hg. Mercurial...

One piece I'm not sure about is where non-Nim dependencies should be added/defined. Would it just be overloading the `requires` in the nimble file and adding it as another dep?...

Ok that makes sense for running the extractors. Would the extractors also be responsible for outputting a list of dependencies/repos then from a Nim project? Alternatively would non-Nim projects be...

No worries on my end, it's a bit overloaded and I'm unsure if it's more of a builders or extractors issue. It's really neither? > But currently you cannot declare...