Skip to content

Conversation

@tvandijck
Copy link
Collaborator

Checklist

  • I have read the Contributor Guide
  • I have read and agree to the Code of Conduct
  • I have added a description of my changes and why I'd like them included in the section below

Description of Changes

Describe your changes here

Related Issues

List related issues here

@tvandijck tvandijck requested a review from arturjpv September 3, 2025 10:52
var returnData = GetDefaultReturnStatementForScope(parentScope);

ServerOnlyScopeData newData = new ServerOnlyScopeData(
ExcisionUtils.FindScriptIndexForCodePoint(Script, simpleDeclaration.Stop.Line, simpleDeclaration.Stop.Column) + 1,
Copy link
Member

@arturjpv arturjpv Sep 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see we are removing these lines and commenting the ShrinkServerScope. I remember doing this correction because of the StartIndex/StopIndex adjustment. Everything behaves ok after removing them?

Copy link
Collaborator Author

@tvandijck tvandijck Sep 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, I'm still working on things, in some very rare cases (like 2 files out of 5000) I end up with double macros... very weird. It's not because of this though.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I added the ShrinkServerScope to avoid the double macro problem here. Not sure about the origin of the FindScriptIndexForCodePoint calls.

@tvandijck tvandijck marked this pull request as draft September 3, 2025 11:50
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