-
Notifications
You must be signed in to change notification settings - Fork 14
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
base: master
Are you sure you want to change the base?
Conversation
264e70f
to
6b127db
Compare
6b127db
to
033647b
Compare
There was a problem hiding this 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.
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 |
0232adf
to
df86b7c
Compare
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. |
df86b7c
to
280f53f
Compare
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
b5ae7dd
to
67552b8
Compare
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. |
This reverts commit 04d0534.
This reverts commit dd7ccfb.
…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
b1f97c5
to
f2008df
Compare
This is the branch that includes all the work necessary to cut over from Discussions V1 to V2 APIs.
Instructions for testing:
Closes Issues: # (if appropriate)
Updated meaningful TSDoc to methods including Parameters and Returns, see Documentation Guide
used semantic commit messages
PR title follows semantic commit format (CRITICAL if the title is not in a semantic format, the release automation will not run!)
updated
peerDependencies
as needed. CRITICAL our automated release system can not be counted on to updatepeerDependencies
so we must do it manually in our PRs when needed. See the updating peerDependencies section of the release instructions for more details.