-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat(elements): new component 'ino-nav-menu' #1148
Draft
iandi09
wants to merge
37
commits into
master
Choose a base branch
from
elements-#1075-ino-nav-menu
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iandi09
changed the title
Elements #1075 ino nav menu
feat(elements): new component 'ino-nav-menu'
Dec 22, 2023
MariaLStefan
requested changes
Jan 9, 2024
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.
packages/elements/src/components/ino-nav-menu-section/ino-nav-menu-section.tsx
Outdated
Show resolved
Hide resolved
packages/elements/src/components/ino-nav-menu/ino-nav-menu.scss
Outdated
Show resolved
Hide resolved
Comment on lines
226
to
227
href={`#${id}`} | ||
onClick={(e) => this.handleAnchorClick(e, id)} |
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.
Do we even need a href
if we prevent the default action through handleAnchorClick
? Or is it needed for accessibility reasons?
packages/storybook/src/stories/ino-nav-menu/ino-nav-menu.stories.ts
Outdated
Show resolved
Hide resolved
packages/storybook/src/stories/ino-nav-menu/ino-nav-menu.stories.ts
Outdated
Show resolved
Hide resolved
MariaLStefan
temporarily deployed
to
github-pages
January 23, 2024 14:48
— with
GitHub Actions
Inactive
MariaLStefan
temporarily deployed
to
github-pages
January 23, 2024 15:53
— with
GitHub Actions
Inactive
- add stories for props `sectionName`, `sectionId` & `showTitle`
- use theme - add word-break for sections - remove nesting - tweak paddings
- add max-height to every story to see stickyness of nav
- intersectionObserverConfig - scrollOffset
…tion - allows multiple instances of ino-nav-menu on one page - add possible loading skeleton div (needs to be visually implemented) - add possibility to use own section IDs
…further up in DOM & show functionality better - add `sectionsRenderObserver` before initiating of `ino-nav-menu` section points - add switch to shrink playground and show stickiness of `ino-nav-menu` - add active-section change
- move skeleton-loading to animation - ino-avatar: use new skeleton-loading mixin
…er to init Sections - add Event Emitter for sectionReady in ino-nav-section - needs fix: activeSection cannot be emitted in autodetect right now - needs fix: story for sections does not work, check setSectionsFromProps
# Conflicts: # packages/elements/src/components.d.ts # packages/landingpage/app/[lang]/getting-started/_components/layout.tsx # packages/landingpage/app/[lang]/getting-started/_components/menuSection.tsx # packages/landingpage/app/[lang]/getting-started/_components/navigationMenu.module.scss # packages/landingpage/app/[lang]/getting-started/_components/navigationMenu.tsx # packages/landingpage/app/[lang]/getting-started/angular/angular-guide.mdx # packages/landingpage/app/[lang]/getting-started/javascript/javascript-guide.mdx # packages/landingpage/app/[lang]/getting-started/react/react-guide.mdx # packages/landingpage/app/[lang]/getting-started/vue/vue-guide.mdx # packages/landingpage/utils/elementsWrapper.ts
janivo
force-pushed
the
elements-#1075-ino-nav-menu
branch
from
March 26, 2024 14:41
23ce579
to
bb90469
Compare
# Conflicts: # packages/elements/src/components/ino-snackbar/readme.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1075
Additions
reInitSections()
for manual re-initiation of sectionsino-nav-menu
lies further up in DOM then their corresponding sectionssectionContainerID
for better autodetection (makes it possible to have multipleino-nav-menu
on one page)sectionID
toino-nav-menu-section
so that consumers can set their own ids. If not set default to build ID From section nameino-nav-menu-section
ino-nav-menu
ino-nav-menu
can be seenintersectionObserverConfig
andscrollOffset
loading
and a skeleton loaderskeleton-loading
animation from ino-avatar to_animation.scss