-
-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
css scope migration #2339
css scope migration #2339
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like you forgot to add iteration scopes. I added them, along with some fixture tests. I also added a few new fixture types while I was here. Worth having a look at those fixture ID's. I think they're logical but they may warrant some discussion. See my changes in https://github.com/cursorless-dev/cursorless/pull/2339/files/13d759c3b090dd3872d2e170701521811b76436d..9496ae08a6f2dc5456e8a15ffca676affd52dc70
Merge if you're happy
data/fixtures/scopes/scss/index.json
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fact that this was missing inspired #2370, which also includes this file
scopeType: "namedFunction", | ||
isIteration: true, | ||
}, | ||
"namedFunction.iteration": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pokey There's no indicator in the name or description what this iteration scope should be. Shouldn't this be namedFunction.iteration.block
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah so the issue is that we don't necessarily want the iteration scope for functions to always include blocks. For example, that's not what we do in typescript. I added this as a catch-all so that I could include blocks for css. Might be worth discussing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can us go ahead and merge this because we can always update later?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Slightly mixed feelings about merging in facet ids that we will want to change, as I think it could be a bit painful to rename them, especially as they get used more
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possibly. Should be punt on this then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm. Would be good to get this PR in, but I think it's going to be easier to get this one right, as we use this facet for this PR. I'd be inclined to discuss Sunday
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On second thought, let's get this thing in. I filed #2375; let's discuss Sunday
Checklist