Skip to content

bar_index extra handling? Just for your consideration. #139#146

Open
dcaoyuan wants to merge 1 commit intoQuantForgeOrg:mainfrom
dcaoyuan:bar_index-question
Open

bar_index extra handling? Just for your consideration. #139#146
dcaoyuan wants to merge 1 commit intoQuantForgeOrg:mainfrom
dcaoyuan:bar_index-question

Conversation

@dcaoyuan
Copy link
Contributor

@dcaoyuan dcaoyuan commented Mar 5, 2026

I noticed your fixing for bar_index: 2712222

Not sure if there are still some changes should be applied. Just for your consideration.

And 'bar_index' is a built-in variable or CONTEXT_DATA_VARS ? which is better?

@dcaoyuan dcaoyuan force-pushed the bar_index-question branch from 5041b4a to 94b86c1 Compare March 5, 2026 03:36
@dcaoyuan dcaoyuan force-pushed the bar_index-question branch from 94b86c1 to 07fafdd Compare March 5, 2026 03:39
@alaa-eddine
Copy link
Collaborator

tbh I'm hesitating, it can fall in both, since it only relies on the bars data.
but at the same time Pine Script has things like last_bar_index too which is not known the moment we parse the current fetched bars.

I'll need to think about it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants