-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
New Design Section Nav Component #11266
New Design Section Nav Component #11266
Conversation
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## design-section-feature-branch #11266 +/- ##
==================================================================
- Coverage 67.07% 47.87% -19.21%
==================================================================
Files 571 157 -414
Lines 21175 5333 -15842
Branches 4236 1064 -3172
==================================================================
- Hits 14203 2553 -11650
+ Misses 6457 2552 -3905
+ Partials 515 228 -287 see 469 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Nice work! Just wondering, could you clarify why you opted for a new There are a few design differences between the existing implementation and this new one (both the panel style and the action button tab style) so we'll need to basically maintain both as duplicates of each other, unless we choose to use one for everything. Not saying that it's a bad decision, but just wondering what your reasoning was for creating duplicate components instead of reusing (and updating if required) the existing one, in case there's a good reason that I haven't thought of. My other question was just around the actual navigation component - it doesn't seem to have been added to the tree, but maybe you were planning on doing that in a separate PR? |
cf5f567
to
dd70a31
Compare
@aptkingston Nope, your correct, that's a much better shout, didn't think to use it. I'll refactor this. Not sure I understand the second point, the component is visible currently, it's just on the right hand side of the screen, the existing navigation component is still present too, but that'll be replaced in another PR. |
Cool, no worries. For the second point I mean the actual "component" in the tree, which is the new way of accessing the navigation settings instead of the existing small icon in the side nav. It would basically just appear as a fake app component, like in this screenshot from the designs: I assumed it would make sense to include that in this PR as well, but maybe you were planning on adding that later. |
e92042e
to
8f322cd
Compare
☁️ Nx Cloud ReportCI is running/has finished running commands for commit bd33c0e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 3 targetsSent with 💌 from NxCloud. |
8f322cd
to
1e7c96f
Compare
1e7c96f
to
7fb818d
Compare
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
7fb818d
to
25a7981
Compare
94c76c1
to
f1017c8
Compare
25a7981
to
bd33c0e
Compare
Description
Adds the new navigation settings panel to the design section as outlined in the ticket. Also implements some new components that will be used by other changes to these panels in future.
Addresses:
https://linear.app/budibase/issue/BUDI-7164/design-section-navigation-component