How to Use a Properties Viewer to Inspect App Settings Quickly
1. Open the Properties Viewer
- Launch the viewer from your IDE, admin console, or app menu.
- Tip: Keyboard shortcuts (e.g., Ctrl+P / Cmd+P) often open it faster.
2. Locate the target object or component
- Navigate to the file, module, UI element, or runtime instance whose settings you need.
- Use search within the viewer to jump directly to a property path (e.g., user.profile.settings).
3. Filter and search properties
- Use the search box to filter by key name or value.
- Apply type or scope filters (e.g., strings, booleans, environment vs. user-level) to reduce noise.
4. Inspect values and metadata
- Read the current value, default value, and data type displayed for each property.
- Check metadata such as last-modified timestamp, source (config file, database, env var), and read-only flags.
5. Expand nested structures
- Click to expand objects, arrays, or maps to inspect nested fields without leaving the viewer.
- Use path breadcrumbs to keep track of where you are in deeply nested data.
6. Compare live vs. default or staged configs
- Toggle views to compare current runtime values with defaults or a staged/previous version.
- Look for unexpected overrides or missing keys.
7. Edit safely when allowed
- Use inline editing for quick changes; prefer staged edits or feature flags for production.
- Validate edits with built-in validators (type checks, allowed ranges) before saving.
8. Apply, test, and revert changes
- Apply changes in a safe environment (dev or staging) first.
- Test the app behavior immediately after applying.
- Use the revert or history feature to roll back if needed.
9. Audit and track changes
- Enable change logging to capture who changed what and when.
- Export snapshots for audits or troubleshooting sessions.
10. Best practices
- Read-only in production: Avoid directly editing production unless absolutely necessary.
- Use descriptive keys: Makes quick inspection faster.
- Group related properties: Logical grouping reduces search time.
- Document critical settings: Keep notes on consequences of changing values.
Quick checklist:
- Open viewer → Locate object → Filter/search → Inspect metadata → Compare versions → Edit in staging → Test → Audit.