-
Notifications
You must be signed in to change notification settings - Fork 4
#262 Interaction Panel Implementation #290
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: main
Are you sure you want to change the base?
Conversation
…use it for action items
…tents and update the stories
…r-dropdown Fix naming for list comopnent
… better organization
merge dictionary component
merge pr suggestions
merge pr changes from header component
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.
couple of small changes to start with.
I'll take a look if there's a cleaner way to do the disabled state being passed in as props everywhere. a context provider might make sense, but adds some complexity.
There's also maybe a slightly cleaner way to compose css with emotion that I will verify.
Because emotion serializes to classNames, you basically create css..
fragments and conditionally apply them using https://www.npmjs.com/package/clsx
packages/ui/src/viewer-table/InteractionPanel/AttributeFilterDropdown.tsx
Outdated
Show resolved
Hide resolved
packages/ui/src/viewer-table/InteractionPanel/DictionaryVersionSwitcher.tsx
Outdated
Show resolved
Hide resolved
packages/ui/src/viewer-table/InteractionPanel/InteractionPanel.tsx
Outdated
Show resolved
Hide resolved
packages/ui/src/viewer-table/InteractionPanel/InteractionPanel.tsx
Outdated
Show resolved
Hide resolved
packages/ui/src/viewer-table/InteractionPanel/InteractionPanel.tsx
Outdated
Show resolved
Hide resolved
…ropdown.tsx Co-authored-by: Ciarán Schütte <[email protected]>
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.
looking good. requesting changes because I'll have to re-approve anyway ;)
// When we are at multiple versions, then the version switcher is now rendered, this is to test that behavior | ||
export const Default: Story = { | ||
args: { | ||
...mockProps, | ||
dictionaryConfig: { | ||
...mockProps.dictionaryConfig, | ||
dictionaryData: MultipleDictionaryData, | ||
}, | ||
}, | ||
}; | ||
|
||
// The reason why this story exists is to test the behavior when the dictionary version switcher button is not rendered | ||
export const WithSingleVersion: Story = { | ||
args: { | ||
...mockProps, | ||
dictionaryConfig: { | ||
...mockProps.dictionaryConfig, | ||
dictionaryData: SingleDictionaryData, |
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.
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.
it'll be storybook decorator likely
Summary
Implementing the rest of the remaining tickets inside of the interaction panel, with the associated stories for appropriate testing
see tickets: #273 and #274 for details on current blocked items
Issues
Description of Changes
Most changes were just porting over the components from
stage
however there are some components that are incomplete/blocked due to requirements that are not yet possible from the present functionality of lectern.Readiness Checklist
.env.schema
file and documented in the README