Skip to content

feat(hub-common): discussions v1 to v2 #1853

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

Open
wants to merge 37 commits into
base: master
Choose a base branch
from

Conversation

rweber-esri
Copy link
Contributor

@rweber-esri rweber-esri commented Apr 3, 2025

  1. Description:

This is the branch that includes all the work necessary to cut over from Discussions V1 to V2 APIs.

  1. Instructions for testing:

  2. Closes Issues: # (if appropriate)

  3. Updated meaningful TSDoc to methods including Parameters and Returns, see Documentation Guide

  4. used semantic commit messages

  5. PR title follows semantic commit format (CRITICAL if the title is not in a semantic format, the release automation will not run!)

  6. updated peerDependencies as needed. CRITICAL our automated release system can not be counted on to update peerDependencies so we must do it manually in our PRs when needed. See the updating peerDependencies section of the release instructions for more details.

@rweber-esri rweber-esri changed the base branch from f/12668-add-entity-discussion-settings-schema to master April 3, 2025 03:16
@rweber-esri rweber-esri force-pushed the f/discussions-v1-to-v2 branch 2 times, most recently from 264e70f to 6b127db Compare April 3, 2025 14:21
@rweber-esri rweber-esri force-pushed the f/discussions-v1-to-v2 branch from 6b127db to 033647b Compare April 7, 2025 12:38
Copy link
Contributor

@tommybramble tommybramble left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No findings from the code review.

Just FYI, the documentation guide link in the PR description is broken for me. I'm assuming that is the same storybook I can see when I run the app locally, but wondering if I should be able to access that link.

@rweber-esri
Copy link
Contributor Author

rweber-esri commented Apr 7, 2025

Just FYI, the documentation guide link in the PR description is broken for me. I'm assuming that is the same storybook I can see when I run the app locally, but wondering if I should be able to access that link.

Thanks for pointing that out @tommybramble, that's been outdated for some time. I've updated the PR template on this branch so that the Documentation Guide link points here. The URL change won't be reflected though until this PR merges.

@rweber-esri rweber-esri force-pushed the f/discussions-v1-to-v2 branch 3 times, most recently from 0232adf to df86b7c Compare April 11, 2025 20:04
Copy link

There hasn't been any activity on this pull request in the past 3 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. If you want this PR to never become stale, please apply the "Draft" label.

@github-actions github-actions bot added the Stale Stale issue - update or it will be closed label Apr 15, 2025
@rweber-esri rweber-esri force-pushed the f/discussions-v1-to-v2 branch from df86b7c to 280f53f Compare April 15, 2025 16:58
@github-actions github-actions bot removed the Stale Stale issue - update or it will be closed label Apr 16, 2025
Copy link

There hasn't been any activity on this pull request in the past 3 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. If you want this PR to never become stale, please apply the "Draft" label.

@github-actions github-actions bot added the Stale Stale issue - update or it will be closed label Apr 21, 2025
Copy link
Contributor

@juliannaeapicella juliannaeapicella left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@github-actions github-actions bot removed the Stale Stale issue - update or it will be closed label Apr 22, 2025
@rweber-esri rweber-esri force-pushed the f/discussions-v1-to-v2 branch 4 times, most recently from b5ae7dd to 67552b8 Compare April 24, 2025 12:54
@rweber-esri rweber-esri changed the title feat(hub-common): expose the allowed channel ids field in the entity … feat(hub-common): discussions v1 to v2 Apr 24, 2025
Copy link

There hasn't been any activity on this pull request in the past 3 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. If you want this PR to never become stale, please apply the "Draft" label.

@github-actions github-actions bot added the Stale Stale issue - update or it will be closed label Apr 28, 2025
@rweber-esri rweber-esri added Draft Draft PR or Issue (don't mark stale) and removed Stale Stale issue - update or it will be closed labels May 2, 2025
rweber-esri and others added 29 commits July 8, 2025 14:39
…ma & uiSchema for group members

affects: @esri/hub-common

ISSUES CLOSED: 12787
affects: @esri/hub-common

ISSUES CLOSED: 12787
affects: @esri/hub-common

ISSUES CLOSED: 12787
…chemaDiscussionSettings uischem

affects: @esri/hub-common

ISSUES CLOSED: 12875
… Members, Group => Members & Gr

affects: @esri/hub-common

ISSUES CLOSED: 12913
…pr-preview for this branch

affects: @esri/hub-common
…g for channels and renaming gro

affects: @esri/hub-common

ISSUES CLOSED: 12667
…panning all category:org channe

affects: @esri/hub-common

ISSUES CLOSED: 12667
…ntially being null

affects: @esri/hub-common

ISSUES CLOSED: 12667
…astActivity

affects: @esri/hub-common

ISSUES CLOSED: 12667
…rather that directly referencin

affects: @esri/hub-common

ISSUES CLOSED: 12667
…g/fetching posts using the Post

affects: @esri/hub-common

ISSUES CLOSED: 12667
affects: @esri/hub-common

ISSUES CLOSED: 12667
… access a channel group's user

affects: @esri/hub-common

ISSUES CLOSED: 12667
… permissions when building grou

affects: @esri/hub-common

ISSUES CLOSED: 12667
…m group admin predicates

affects: @esri/hub-common

ISSUES CLOSED: 12667
affects: @esri/hub-common

ISSUES CLOSED: 12667
…y fn

affects: @esri/hub-common

ISSUES CLOSED: 13549
…errors related to no filters be

affects: @esri/hub-common

ISSUES CLOSED: 12667
…a hubSearch

affects: @esri/hub-common

ISSUES CLOSED: 12667
…mine if the user is not authori

affects: @esri/hub-common

ISSUES CLOSED: 12667
affects: @esri/hub-common

ISSUES CLOSED: 12667
affects: @esri/hub-common

ISSUES CLOSED: 12667
affects: @esri/hub-common

ISSUES CLOSED: 12667
@rweber-esri rweber-esri force-pushed the f/discussions-v1-to-v2 branch from b1f97c5 to f2008df Compare July 8, 2025 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Draft Draft PR or Issue (don't mark stale)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants