Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: merge develop into main #1505

Merged
merged 9 commits into from
Dec 10, 2024
Merged

chore: merge develop into main #1505

merged 9 commits into from
Dec 10, 2024

Conversation

soleksy-splunk
Copy link
Contributor

No description provided.

soleksy-splunk and others added 9 commits November 27, 2024 16:48
Co-authored-by: Viktor Tsvetkov <[email protected]>
**Issue number:**
N/A
### PR Type

**What kind of change does this PR introduce?**
* [ ] Feature
* [ ] Bug Fix
* [ ] Refactoring (no functional or API changes)
* [ ] Documentation Update
* [x] Maintenance (dependency updates, CI, etc.)

## Summary
Configuration for documentation lint.
### Changes

Please provide a summary of the changes.
use asterisk as bold sign
### User experience

Please describe the user experience before and after this change.
Screenshots are welcome for additional context.
N/A
## Checklist

If an item doesn't apply to your changes, leave it unchecked.

* [x] I have performed a self-review of this change according to the
[development
guidelines](https://splunk.github.io/addonfactory-ucc-generator/contributing/#development-guidelines)
* [x] Tests have been added/modified to cover the changes [(testing
doc)](https://splunk.github.io/addonfactory-ucc-generator/contributing/#build-and-test)
* [ ] Changes are documented
* [x] PR title and description follows the [contributing
principles](https://splunk.github.io/addonfactory-ucc-generator/contributing/#pull-requests)
**Issue number:** ADDON-76501

### PR Type

**What kind of change does this PR introduce?**
* [x] Feature
* [ ] Bug Fix
* [ ] Refactoring (no functional or API changes)
* [x] Documentation Update
* [ ] Maintenance (dependency updates, CI, etc.)

## Summary
Provided an optional flag `--include-author` in `ucc-gen init` command
to add an author name in `app.manifest`.

### Changes

Introduced an optional flag `--include-author` in the `ucc-gen init`
command, it allows users to specify the name of the author during
initialization of add-on.
The author's name will appear in `app.manifest` under `info -> author ->
name` and in `app.conf` (after building your add-on) under `launcher ->
author` field.

### User experience
Users can now specify the author name using this flag and include them
in their `app.manifest`.

## Checklist

If an item doesn't apply to your changes, leave it unchecked.

* [x] I have performed a self-review of this change according to the
[development
guidelines](https://splunk.github.io/addonfactory-ucc-generator/contributing/#development-guidelines)
* [x] Tests have been added/modified to cover the changes [(testing
doc)](https://splunk.github.io/addonfactory-ucc-generator/contributing/#build-and-test)
* [x] Changes are documented
* [x] PR title and description follows the [contributing
principles](https://splunk.github.io/addonfactory-ucc-generator/contributing/#pull-requests)
**Issue number:**
N/A
### PR Type

**What kind of change does this PR introduce?**
* [ ] Feature
* [x] Bug Fix
* [ ] Refactoring (no functional or API changes)
* [ ] Documentation Update
* [ ] Maintenance (dependency updates, CI, etc.)

## Summary

Modifications did not work for fields inside any group.

### Changes

Pass all parameters when rendering groups.

Please provide a summary of the changes.

### User experience

Modifications works correctly when using groups.

Please describe the user experience before and after this change.
Screenshots are welcome for additional context.

## Checklist

If an item doesn't apply to your changes, leave it unchecked.

* [x] I have performed a self-review of this change according to the
[development
guidelines](https://splunk.github.io/addonfactory-ucc-generator/contributing/#development-guidelines)
* [x] Tests have been added/modified to cover the changes [(testing
doc)](https://splunk.github.io/addonfactory-ucc-generator/contributing/#build-and-test)
* [ ] Changes are documented
* [x] PR title and description follows the [contributing
principles](https://splunk.github.io/addonfactory-ucc-generator/contributing/#pull-requests)

---------

Co-authored-by: srv-rr-github-token <[email protected]>
**Issue number:**
https://splunk.atlassian.net/browse/ADDON-76687 
### PR Type

**What kind of change does this PR introduce?**
* [x] Feature
* [ ] Bug Fix
* [ ] Refactoring (no functional or API changes)
* [ ] Documentation Update
* [ ] Maintenance (dependency updates, CI, etc.)

## Summary

### Changes

Remove verification to block field from applying modification to itself
after value change.
It is not a risk to allow users to modify field itself as we should be
concerned only for value. (it is still not a problem but seems like a
bad approach to solving problems).

It also enables circular dependencies in case where modifications are
not about value. (modifying values still should work good but seems like
a bad practise)

### User experience

User can right now modify state of field by applying changes to
currently edited field, it allows to create ie. much more useful labels
and help messages referencing value change.

## Checklist

If an item doesn't apply to your changes, leave it unchecked.

* [ ] I have performed a self-review of this change according to the
[development
guidelines](https://splunk.github.io/addonfactory-ucc-generator/contributing/#development-guidelines)
* [x] Tests have been added/modified to cover the changes [(testing
doc)](https://splunk.github.io/addonfactory-ucc-generator/contributing/#build-and-test)
* [ ] Changes are documented
* [x] PR title and description follows the [contributing
principles](https://splunk.github.io/addonfactory-ucc-generator/contributing/#pull-requests)

---------

Co-authored-by: srv-rr-github-token <[email protected]>
**Issue number:**
N/A
### PR Type

**What kind of change does this PR introduce?**
* [ ] Feature
* [ ] Bug Fix
* [ ] Refactoring (no functional or API changes)
* [ ] Documentation Update
* [x] Maintenance (dependency updates, CI, etc.)

## Summary

Allows users to use assistance technologies for disabled buttons and
text fields.

### Changes

Adapt to documentation suggestion to use "dimmed" option for disabled
fields:

[Text](https://splunkui.splunk.com/Packages/react-ui/Text?section=examples#Dimmed)


[Button](https://splunkui.splunk.com/Packages/react-ui/Button?section=examples#Dimmed)

### User experience

Users can navigate by disabled buttons and text fields by using tab. 
## Checklist

If an item doesn't apply to your changes, leave it unchecked.

* [x] I have performed a self-review of this change according to the
[development
guidelines](https://splunk.github.io/addonfactory-ucc-generator/contributing/#development-guidelines)
* [ ] Tests have been added/modified to cover the changes [(testing
doc)](https://splunk.github.io/addonfactory-ucc-generator/contributing/#build-and-test)
* [ ] Changes are documented
* [x] PR title and description follows the [contributing
principles](https://splunk.github.io/addonfactory-ucc-generator/contributing/#pull-requests)

---------

Co-authored-by: srv-rr-github-token <[email protected]>
@soleksy-splunk soleksy-splunk merged commit f656c70 into main Dec 10, 2024
120 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Dec 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants