Open
Conversation
KiaraGrouwstra
force-pushed
the
feat/home-manager-options
branch
3 times, most recently
from
981aa1d to
7fb3346
Compare
Contributor
Collaborator
Author
|
screenshot of this in action: 
|
Member
|
Looks great to me! I've approved #1201 |
KiaraGrouwstra
force-pushed
the
feat/home-manager-options
branch
from
7fb3346 to
60c1909
Compare
Collaborator
Author
|
should the new index be available yet? the deployed demo here seems not to be getting results yet |
Member
|
Had a look, looks like #1201 was missing the |
Member
|
the index should now be populated, and indeed https://69dd09ea1ee76aac8f032035--nixos-search.netlify.app/options?channel=unstable&include_home_manager_options=1&include_modular_service_options=1&include_nixos_options=1&query=nix no longer produces 404's, but it also doesn't show any home-manager options |
KiaraGrouwstra
force-pushed
the
feat/home-manager-options
branch
from
60c1909 to
3de4619
Compare
KiaraGrouwstra
force-pushed
the
feat/home-manager-options
branch
from
e75d21c to
f6fa59a
Compare
Evaluate home-manager options during the nixpkgs channel import so they land in the same Elasticsearch index as NixOS options and modular services. This makes them visible to the frontend without requiring cross-index queries. - Add `get_home_manager_options()` to the nixpkgs import path, using `--override-flake` to resolve the home-manager flake - Add `NixpkgsEntry::HomeManagerOption` and its `Derivation` conversion - Remove `FlakeEntry::HomeManagerOption` (no longer needed on the flake import path) - Remove `home-manager-options` from `flake_info.nix`'s `all` attribute to avoid duplicating them in the group-manual index - Bump import schema version to 47
Add a "Home Manager" checkbox to the Options page sidebar alongside the existing NixOS and Modular services toggles, handled identically via the `OptionSource` mechanism. - Add `HomeManagerOptionSource` variant to `OptionSource` with ES document type `home-manager-option` - Switch `excludedOptionSources` to `includedOptionSources` throughout Route, Search, Main, and Options for clearer positive-set semantics - Add `docType` field to `ResultItemSource` (decoded from ES `type`) to distinguish option kinds without metadata heuristics - Use `docType:name` as the option identity for expand/collapse, so identically-named options from different sources toggle independently - Show pill badges (NixOS / Service / HM) when multiple categories are enabled in the filter - Add Usage snippets with `_class` for all three option types - Bump frontend schema version to 47
KiaraGrouwstra
force-pushed
the
feat/home-manager-options
branch
from
f6fa59a to
5c80948
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
filing these together
as draftto hopefully get the working demo up - first part (back) filed separately at #1201.edit: maybe draft won't deploy? trying marked ready now.
okay i guess deployment wouldn't work until the back-end has been populated with the needed info? marking as draft again then.