getlantern / getlantern/unbounded
Rename the UI interface to better represent its current functionality
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 57
- Forks
- 1
- Avg merge
- 20h 26m
- Merged PRs (30d)
- 13
Description
The UI interface is mutating and expanding. Now, it's really a cross-platform abstraction layer that exposes the Broflake API to developers across runtime environments.
The UIImpl struct keeps a reference to a Broflake struct, but this is probably an inside-out way of looking at how things work.
A UIImpl should be called Broflake, and what we currently call Broflake actually represents something that might more accurately be called BroflakeEngine -- that is, it's tables and routers and the technical guts of an instance of a client.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the repository for the UI, UIImpl, and Broflake definitions and all references to them. Read how UIImpl relates to Broflake before applying the proposed naming split, then verify that the renamed API abstraction and engine references remain consistent across runtime environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100