confluence-cli 1.20.0 → 1.21.0

package/llms.txt

@@ -1,46 +0,0 @@
-# Confluence CLI
-
-> A powerful command-line interface for Atlassian Confluence that allows you to read, search, and manage your Confluence content from the terminal.
-
-This CLI tool provides a comprehensive set of commands for interacting with Confluence. Key features include creating, reading, updating, and searching for pages. It supports various content formats like markdown and HTML.
-
-To get started, install the tool via npm and initialize the configuration:
-```sh
-npm install -g confluence-cli
-confluence init
-```
-
-## Documentation
-
-- [README.md](./README.md): Main documentation with installation, usage, and command reference.
-
-## Core Source Code
-
-- [bin/confluence.js](./bin/confluence.js): The main entry point for the CLI, defines commands and argument parsing.
-- [lib/confluence-client.js](./lib/confluence-client.js): The client library for interacting with the Confluence REST API.
-- [package.json](./package.json): Project metadata, dependencies, and scripts.
-
-## Recent Changes & Fixes
-
-This section summarizes recent improvements to align the codebase with its documentation and fix bugs.
-
-### `update` Command Logic and Documentation:
-- **Inconsistency:** The `README.md` suggested that updating a page's title without changing its content was possible. However, the implementation in `bin/confluence.js` incorrectly threw an error if the `--content` or `--file` flags were not provided, making title-only updates impossible.
-- **Fix:**
-    - Modified `updatePage` in `lib/confluence-client.js` to fetch and re-use existing page content if no new content is provided.
-    - Adjusted validation in `bin/confluence.js` for the `update` command to only require one of `--title`, `--content`, or `--file`.
-    - Updated `README.md` with an example of a title-only update.
-
-### Incomplete `README.md` Command Reference:
-- **Inconsistency:** The main command table in `README.md` was missing several commands (`create`, `create-child`, `update`, `edit`, `find`).
-- **Fix:** Expanded the command table in `README.md` to include all available commands.
-
-### Misleading `read` Command URL Examples:
-- **Inconsistency:** The documentation for the `read` command used "display" or "pretty" URLs, which are not supported by the `extractPageId` function.
-- **Fix:** Removed incorrect URL examples and clarified that only URLs with a `pageId` query parameter are supported.
-
-## Next Steps
-
-- Refer to [README.md](./README.md) for detailed usage instructions and advanced configuration.
-- For troubleshooting or to contribute, visit the project's GitHub repository at https://github.com/pchuri/confluence-cli.
-- If you encounter issues, open an issue or check the FAQ section in the documentation.

package/tests/config.test.js

@@ -1,79 +0,0 @@
-const { getConfig } = require('../lib/config');
-
-// Save and restore all relevant env vars around each test
-const ENV_KEYS = [
-  'CONFLUENCE_DOMAIN', 'CONFLUENCE_HOST',
-  'CONFLUENCE_API_TOKEN', 'CONFLUENCE_PASSWORD',
-  'CONFLUENCE_EMAIL', 'CONFLUENCE_USERNAME',
-  'CONFLUENCE_AUTH_TYPE', 'CONFLUENCE_API_PATH'
-];
-
-describe('getConfig env var aliases', () => {
-  const saved = {};
-
-  beforeEach(() => {
-    for (const key of ENV_KEYS) {
-      saved[key] = process.env[key];
-      delete process.env[key];
-    }
-  });
-
-  afterEach(() => {
-    for (const key of ENV_KEYS) {
-      if (saved[key] !== undefined) {
-        process.env[key] = saved[key];
-      } else {
-        delete process.env[key];
-      }
-    }
-  });
-
-  test('CONFLUENCE_USERNAME is used when CONFLUENCE_EMAIL is not set', () => {
-    process.env.CONFLUENCE_DOMAIN = 'on-prem.example.com';
-    process.env.CONFLUENCE_PASSWORD = 'secret';
-    process.env.CONFLUENCE_USERNAME = 'admin';
-    process.env.CONFLUENCE_AUTH_TYPE = 'basic';
-
-    const config = getConfig();
-    expect(config.email).toBe('admin');
-    expect(config.token).toBe('secret');
-  });
-
-  test('CONFLUENCE_EMAIL takes priority over CONFLUENCE_USERNAME', () => {
-    process.env.CONFLUENCE_DOMAIN = 'cloud.atlassian.net';
-    process.env.CONFLUENCE_API_TOKEN = 'api-token';
-    process.env.CONFLUENCE_EMAIL = 'user@example.com';
-    process.env.CONFLUENCE_USERNAME = 'admin';
-    process.env.CONFLUENCE_AUTH_TYPE = 'basic';
-
-    const config = getConfig();
-    expect(config.email).toBe('user@example.com');
-  });
-
-  test('CONFLUENCE_PASSWORD is used when CONFLUENCE_API_TOKEN is not set', () => {
-    process.env.CONFLUENCE_DOMAIN = 'on-prem.example.com';
-    process.env.CONFLUENCE_PASSWORD = 'my-password';
-    process.env.CONFLUENCE_USERNAME = 'admin';
-    process.env.CONFLUENCE_AUTH_TYPE = 'basic';
-
-    const config = getConfig();
-    expect(config.token).toBe('my-password');
-  });
-
-  test('CONFLUENCE_API_TOKEN takes priority over CONFLUENCE_PASSWORD', () => {
-    process.env.CONFLUENCE_DOMAIN = 'cloud.atlassian.net';
-    process.env.CONFLUENCE_API_TOKEN = 'api-token';
-    process.env.CONFLUENCE_PASSWORD = 'password';
-
-    const config = getConfig();
-    expect(config.token).toBe('api-token');
-  });
-
-  test('CONFLUENCE_HOST alias still works for domain', () => {
-    process.env.CONFLUENCE_HOST = 'host.example.com';
-    process.env.CONFLUENCE_API_TOKEN = 'token';
-
-    const config = getConfig();
-    expect(config.domain).toBe('host.example.com');
-  });
-});