Skip to content
This repository has been archived by the owner on Feb 4, 2022. It is now read-only.

Allow easy access to Alpine JS component data #281

Open
amazeika opened this issue Aug 4, 2021 · 0 comments · May be fixed by #282
Open

Allow easy access to Alpine JS component data #281

amazeika opened this issue Aug 4, 2021 · 0 comments · May be fixed by #282
Assignees
@amazeika
Labels
feature
Milestone
3.1

Comments

@amazeika
Copy link
Contributor

amazeika commented Aug 4, 2021

Client extensions for exposing Alpine JS data don't work quite while. It's always useful and sometimes necessary to have access to this data for helping on developing and debugging a UI.

This feature exposes the Alpine JS component data through a kAlpine global variable that can be accessed and changed on the client inspector.
@amazeika amazeika added this to the 3.1 milestone Aug 4, 2021
@amazeika amazeika self-assigned this Aug 4, 2021
amazeika added a commit that referenced this issue Aug 4, 2021
@amazeika
#281 Expose component data through kAlpine
c9a7582
@github-actions github-actions bot linked a pull request Aug 4, 2021 that will close this issue
Open
amazeika added a commit that referenced this issue Aug 4, 2021
@amazeika
#281 Expose component data through kAlpine
6a42e65
amazeika added a commit that referenced this issue Aug 4, 2021
@amazeika
#281 Add sanity check
f8169e1
amazeika added a commit that referenced this issue Aug 5, 2021
@amazeika
#281 Improvement
b86adec 
- Query for all components in the document
- Do not limit component instantiation on section blocks
- Properly assign kAlpine variable depending on the number of components present on the document
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@amazeika amazeika

Labels
feature
Projects
None yet
Milestone
3.1
Development

Successfully merging a pull request may close this issue.

Allow easy access to Alpine JS component data timble/kodekit
1 participant
@amazeika