Mastersam07 / Mastersam07/kaisel

Question: How to provide something to a single or multiple screens?

Open
#91 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dart
Stars
69
Forks
2
Avg merge
18m
Merged PRs (30d)
9

Description

I've took some time to experiment with this package.

It's surely interesting, but I think the package is still young and I've found a little hard to achieve some things.

Example: I want to wrap a group of screens with a Provider (a BlocProvider to be precise, but it could've been a RepositoryProvider, a Listenable, anything that I want to be visibile from the context).

For this, I have to group the routes into a sealed class group, so I can provide a KaiselShell of this sealed subclass, just to be able to use the chromeBuilder.

But now I've spawned another navigator, since I have a KaiselShell with a single shell, and the default back buttons from the Scaffolds are broken.

Maybe I'm trying to apply the wrong pattern here, I don't know, but providing things with context is a basic thing to do in Flutter.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing KaiselShell, chromeBuilder, sealed route groups, and nested navigator handling in the project. Reproduce the single-shell case described in the issue and determine the supported way to expose providers to one or more screens while keeping Scaffold back buttons working; no file or test is named.

Written by the indexing model from the issue text.

Assessment

Tech stack
dart, flutter
Domain
mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.