Repository navigation
feat(xerj): default Mobile startup to automatic indexing - #135
Merged
Merged
Conversation
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
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.
Starting Mobile without
--xerjnow selectsauto, enabling background indexing and watching of the configured source root. Explicit--xerj manualand--xerj offcontinue to override the default.Update default configuration expectations, CLI help, README, and XERJ documentation. Existing tests cover explicit selection of all three modes and invalid-mode rejection.
Validation:
npm test— 2,728 passed, 2 skipped across 343 passing test files and 2 skipped files.npm run format:check,npm run license:check,npm run check,npm run lint, andnpm run build— passed.git diff --check— passed.No browser component or relay flow was changed; the browser suite was not run. This changes the startup default only; it does not address the separately reported generic watcher exit, whose underlying native error is still unknown. No running Mobile instance was restarted or modified.